Try the RankNibbler SEO API

Analysis list Beta

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

The recent diagnoses for a monitor, newest first: what we found when each outage was investigated.

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.

Read-only: anything other than GET returns 405.

Path parameters

NameTypeDescription
id requiredstringThe monitor id, for example mon_79ce3cf9c4fa56e98af4.

Query parameters

NameTypeDescription
limit optionalintegerHow many to return, 1 to 100. Default 20.

Request

Response

200 · application/json
  1. {
  2. "id": "mon_79ce3cf9c4fa56e98af4",
  3. "total": 2,
  4. "analyses": [
  5. {
  6. "id": "an_7c1e04b93af2d5608a",
  7. "monitorId": "mon_79ce3cf9c4fa56e98af4",
  8. "cause": "tls",
  9. "summary": "The certificate expired 2 days ago",
  10. "createdAt": "2026-09-16T22:28:04.117Z"
  11. },
  12. {
  13. "id": "an_3ab8d520f16c9e74b1",
  14. "monitorId": "mon_79ce3cf9c4fa56e98af4",
  15. "cause": "tcp",
  16. "summary": "The port refused the connection",
  17. "createdAt": "2026-09-02T09:11:40.880Z"
  18. }
  19. ],
  20. "usage": { "used": 54, "dailyLimit": 100, "tier": "free" }
  21. }

Response fields

FieldTypeDescription
idstringThe monitor id you asked about.
totalintegerHow many diagnoses came back, up to limit.
analyses[].idstringThe diagnosis id, starting an_. Pass it to get one in full.
analyses[].monitorIdstringThe monitor it belongs to.
analyses[].causestringdns, tcp, tls, http, protocol or none. See reading the result.
analyses[].summarystringThe one-line explanation, up to 300 characters.
analyses[].createdAtstringWhen the diagnosis ran.

An empty analyses list means nothing has been diagnosed for this monitor: it may never have gone down, or the outages may be older than the 90 days we keep.

Errors

StatusWhen
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.
405Anything other than GET.
429A rate limit or your daily quota was hit. Read Retry-After, in seconds.
500, 503Something went wrong, or the API is temporarily unavailable. Try again.

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

Related

← Previous
Diagnostics