hosting
GET /v1/uptime/monitors
The web addresses this organisation has asked us to watch.
Authentication
Send an API key as a bearer token. This endpoint does not state a specific permission in the specification, so give your key the least it needs and check the response rather than assuming.
Where your organisation id goes
This endpoint takes org_id as a query parameter. Leave it out and the call covers your whole tenancy subtree; send it to narrow the call to one organisation.
Your organisation id is on the API keys screen in your dashboard, beside the key itself. It is the same id in every call you make.
Try it
Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.
curl -X GET https://api.zinndigital.com/v1/uptime/monitors \
-H "Authorization: Bearer zdk_live_…"Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console
Details
Every monitored URL in scope with its current state and its 30-day headline numbers, plus the organisation's allowance. ⛔ `summary.uptime_percent` is **null** until there is anything to divide, and `summary.checks` travels beside it so a client can render "not enough data yet" rather than a confident 100% — a monitor added a minute ago has proved nothing. Gated on `sites.view`.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
org_id (query) | string | No | Narrow to one organisation in the caller's subtree — what the dashboard's org switcher sends. ⛔ **Narrow only:** intersected with what the caller may already read, so an org out… |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
data | UptimeMonitor[] | Yes | — |
allowance | UptimeAllowance | Yes | — |
Errors this endpoint can return
401 · 403