Uptime monitoring API. Homepage status and incident history for your own dashboard.

Uptime endpoints in REST and the MCP server

Send a POST with a JSON body or a GET with query parameters to /rest/v1/. Your personal API key goes in the header as a Bearer token. Pass the site_id from list_sites or copy it from the site's address in the app. In Claude Code or Cursor, the three MCP tools read the same data.

What a call to uptime.status returns

The call takes only site_id.

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

{
  "data": {
    "enabled": true,
    "url": "https://example-site.nl/",
    "state": "up",
    "up_since": "2026-10-27T23:30:03Z",
    "down_since": null,
    "last_check_at": "2026-10-31T23:00:08Z",
    "certificate_expires_at": "2027-01-01T13:27:24Z",
    "uptime_7d_pct": 100,
    "uptime_30d_pct": 100,
    "response_ms_median_7d": 209,
    "incidents_30d": 1
  },
  "meta": {
    "site_id": "YOUR_SITE_ID"
  }
}

Notice that uptime_30d_pct is 100 here even though incidents_30d is 1. Earlier that week a firewall challenge refused the checker with a 403 (blocked). Any run that was not up lands in uptime.incidents, so you catch firewall blocks too. The uptime percentage only drops when checks come back down.

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.

uptime.status

POST /rest/v1/uptime.status · MCP tool get_uptime_status

Returns the uptime monitor of one site: whether it is on, the checked address (the homepage), the current state, since when it is up or down, the last check, when the SSL certificate expires, the share of checks that were not down over 7 and 30 days, the median response time over 7 days and the number of incidents in 30 days. Values are null while the monitor has no checks yet.

Arguments

Example request

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

Example response · A real answer of 1 November 2026, anonymised: up since a firewall rule was fixed on 28 October.

{
  "data": {
    "enabled": true,
    "url": "https://example-site.nl/",
    "state": "up",
    "up_since": "2026-10-27T23:30:03Z",
    "down_since": null,
    "last_check_at": "2026-10-31T23:00:08Z",
    "certificate_expires_at": "2027-01-01T13:27:24Z",
    "uptime_7d_pct": 100,
    "uptime_30d_pct": 100,
    "response_ms_median_7d": 209,
    "incidents_30d": 1
  },
  "meta": {"site_id": "YOUR_SITE_ID"}
}

Response fields · in data:

uptime.incidents

POST /rest/v1/uptime.incidents · MCP tool get_uptime_incidents

Returns the incidents of the last 30 days, newest first: each run of checks in a row that were not up, with when it started and ended, how long it took, the worst outcome and the HTTP status or error of that check. One failed round already counts here; the site is only marked down (and alerts are sent) after two in a row. An ongoing incident has no end.

Arguments

Example request

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

Example response · The firewall challenge of 26-27 October (403, blocked), before the Skip rule moved to the top of the Cloudflare rules.

{
  "data": [
    {
      "started_at": "2026-10-26T21:22:37Z",
      "ended_at": "2026-10-27T23:30:03Z",
      "ongoing": false,
      "minutes": 1567,
      "outcome": "blocked",
      "rounds": 54,
      "http_status": 403,
      "error": null,
      "firewall": true
    }
  ],
  "meta": {"site_id": "YOUR_SITE_ID", "next_cursor": null, "total": 1}
}

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

uptime.checks

POST /rest/v1/uptime.checks · MCP tool get_uptime_checks

Returns every check of the last 7 days, newest first, with its outcome and response time (time to first byte). The response time is null when the check got no answer.

Arguments

Example request

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

Example response · Shortened to two checks; the real answer had 246.

{
  "data": [
    {"at": "2026-10-31T22:30:06Z", "outcome": "up", "response_ms": 220},
    {"at": "2026-10-31T22:00:07Z", "outcome": "up", "response_ms": 273}
  ],
  "meta": {"site_id": "YOUR_SITE_ID", "next_cursor": null, "total": 246}
}

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