Website alerts API. Every site event from the last 90 days in one feed.

Website alerts endpoints and MCP tools

Call the REST endpoints over HTTPS with POST and a JSON body, or GET with the same arguments in the query string. Send your personal API key from the MCP page in the app as an Authorization: Bearer header. The full REST schema is in the OpenAPI specification. In Claude Code or Cursor, the MCP server exposes the same data as two tools.

You get 60 calls per minute per key across the REST API and the MCP server together. Both endpoints only read data, so a key can never change a site or edit notification settings.

A real alerts.feed call and response

Pass site_id to alerts.feed, and add filters when you only want one slice. This call asks for the last two SEO changes on a site.

curl -s https://app.marketingtracer.com/rest/v1/alerts.feed \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "site_id": "65a1b2c3d4e5f60718293a4b",
    "kind": "seo",
    "limit": 2
  }'

{
  "data": [
    {
      "id": "6ae67516bf737c062606238a",
      "at": "2026-10-31T23:00:00Z",
      "kind": "seo",
      "type": "seo",
      "rule": "status_change",
      "label": "changed",
      "text": "Now returns 200 (was 403)",
      "url": "https://www.example-site.nl/pregnancy/work/risk-assessment",
      "open": false
    },
    {
      "id": "6ae5fa7c532767cc8602b59b",
      "at": "2026-10-30T23:00:00Z",
      "kind": "seo",
      "type": "seo",
      "rule": "status_change",
      "label": "problem",
      "text": "Now returns 410 (was 403)",
      "url": "https://www.example-site.nl/pregnancy/fun/spa-treatment",
      "open": false
    }
  ],
  "meta": {
    "site_id": "65a1b2c3d4e5f60718293a4b",
    "next_cursor": "eyJwYyI6WzE3OTM0MDEyMDAwMDAs…",
    "total": 2
  }
}

Each row carries a ready-made sentence in text, in English by default or in Dutch with lang: "nl". You also get label (down, problem, worse, fixed or changed) to colour or filter rows right away. SEO events carry the page address in url and the scan key in rule, while site-wide events return null for both. Active outages, blocked checks and SSL or https problems keep open: true until they clear, and SEO rows always have open: false.

The feed reads the site's 90-day history directly, independent of who turned email or Slack alerts on or off in the app. Pass meta.next_cursor back as cursor to load the next page.

Endpoints, arguments and field descriptions

Every endpoint is a POST with a JSON body; reading endpoints also take a GET with the same arguments in the query string. Send your API key as Authorization: Bearer YOUR_API_KEY. Every answer is {"data": …, "meta": {…}}: meta.site_id always, meta.next_cursor and meta.total for a list, meta.period where the endpoint covers a period. An error is {"error": {"code", "message"}} with the HTTP status: 400 invalid_argument, unknown_argument or missing_argument; 401 not_authenticated; 403 no_access or tool_off; 404 not_found; 429 rate_limited. The machine-readable version is openapi.json.

alerts.feed

POST /rest/v1/alerts.feed · MCP tool get_alerts_feed

Returns everything that happened on one site in the last 90 days, newest first, one row per event: outages, SSL and https problems, Core Web Vitals that got worse, and every change the SEO scan found on a page (a new problem, a fixed one, a changed title, H1, meta description or status). The same rows as the Meldingen page, independent of who gets which alert by mail or Slack. Page through with cursor.

Arguments

Example request

curl -X POST https://app.marketingtracer.com/rest/v1/alerts.feed \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"site_id":"YOUR_SITE_ID","kind":"seo","limit":2}'

Example response · Two SEO rows; pages that came back after the firewall fix.

{
  "data": [
    {
      "id": "6ae67516bf737c062606238a",
      "at": "2026-10-31T23:00:00Z",
      "kind": "seo",
      "type": "seo",
      "rule": "status_change",
      "label": "changed",
      "text": "Now returns 200 (was 403)",
      "url": "https://www.example-site.nl/pregnancy/work/risk-assessment",
      "open": false
    },
    {
      "id": "6ae5fa7c532767cc8602b59b",
      "at": "2026-10-30T23:00:00Z",
      "kind": "seo",
      "type": "seo",
      "rule": "status_change",
      "label": "problem",
      "text": "Now returns 410 (was 403)",
      "url": "https://www.example-site.nl/pregnancy/fun/spa-treatment",
      "open": false
    }
  ],
  "meta": {
    "site_id": "YOUR_SITE_ID",
    "next_cursor": "eyJwYyI6WzE3OTM0MDEyMDAwMDAsIjZhZTVmYTdjNTMyNzY3Y2M4NjAyYjU5YiJdfQ==",
    "total": 2
  }
}

Response fields · data is a list; each item has:

alerts.summary

POST /rest/v1/alerts.summary · MCP tool get_alerts_summary

Returns how many events the site had per kind in the last 90 days (the rows of alerts.feed) and what is still going on now: an outage, a blocked check, an SSL or https problem, at most 5, newest first.

Arguments

Example request

curl -X POST https://app.marketingtracer.com/rest/v1/alerts.summary \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"site_id":"YOUR_SITE_ID"}'

Example response · Nothing open; 426 SEO changes in 90 days.

{
  "data": {
    "days": 90,
    "total": 426,
    "by_kind": {"uptime": 0, "sitecheck": 0, "seo": 426, "cwv": 0},
    "open": []
  },
  "meta": {"site_id": "YOUR_SITE_ID"}
}

Response fields · in data: