Try the RankNibbler SEO API

Probes report Beta

GET /api/v1/monitors/{id}/probes

Which locations checked the monitor in the window, how often, and how fast it responded from each.

Needs an X-API-Key header whose owner has access to uptime monitoring in the app. The call counts once against your daily quota. See Monitoring API: getting started for authentication, rate limits and errors.

Query parameters

NameTypeDescription
from optionalstring | integerStart of the window. Default: 7 days before to.
to optionalstring | integerEnd of the window. Default: now. The window can be up to 1830 days.

Request

Response

200 · application/json
  1. {
  2. "id": "mon_79ce3cf9c4fa56e98af4",
  3. "from": "2026-09-10T09:31:00.000Z",
  4. "to": "2026-09-17T09:31:00.000Z",
  5. "probes": [
  6. { "region": "default", "label": "United Kingdom", "checks": 336, "upChecks": 335,
  7. "avgResponseMs": 188, "lastCheckedAt": "2026-09-17T09:30:04.221Z" },
  8. { "region": "eu", "label": "Europe", "checks": 336, "upChecks": 336,
  9. "avgResponseMs": 241, "lastCheckedAt": "2026-09-17T09:15:03.870Z" }
  10. ],
  11. "usage": { "used": 26, "dailyLimit": 100, "tier": "free" }
  12. }

Locations are sorted by number of checks, busiest first, and only locations that ran at least one check are listed. avgResponseMs uses successful checks only. lastCheckedAt is null for windows longer than 92 days, which are read from daily totals.

Errors

StatusWhen
400from or to isn't a valid time, from isn't before to, the window is too long.
401The API key is missing or invalid.
403The key's owner doesn't have access to uptime monitoring, or the key isn't linked to a workspace.
404No monitor with that id in your workspace.
405The endpoint doesn't accept that method.
429A rate limit or your daily quota was hit. Read Retry-After, in seconds.
500Something went wrong on our side. Try again.
503The API is temporarily unavailable. Try again shortly.

Errors are JSON: { "error": "message" }. See Monitoring API errors.

Related