Get monitoring history
Uptime and latency series for a customer’s targets over 24h, 7d or 30d, optionally for one region or target.
Deprecated aliases: GET https://one.vigilbase.com/api/customers/{id}/monitoring/history. They answer with the same bodies, with a Deprecation header and a successor-version link to this URL.
Authorizations
Send one of these:
Bearer access token from Vigilbase Identity (auth.vigilbase.com), sent as Authorization: Bearer <token>. The CLI gets one with vigilbase login. Scope: one:api.
Organisation API key (vb_one_…) from Settings → API keys in Vigilbase One, sent as Authorization: Bearer vb_one_…. Read-only keys work. See organisation API keys.
Vigilbase Identity access token issued to an MCP client (mcp.vigilbase.com). Scope: one:read.
Path Parameters
Query Parameters
24h7d30dDefault:"7d"Probe region code, e.g. nyc, lon, sgp.
Response
application/jsonSuccess
24h7d30dUptime percentage, 0–100.
2 child attributes
Epoch milliseconds.
Latency in milliseconds.
2 child attributes
Epoch milliseconds.
Per-target series for the first five targets with data.
4 child attributes
2 child attributes
Epoch milliseconds.
2 child attributes
Epoch milliseconds.
3 child attributes
True when some per-target series are missing.
2 response headers
The request ID: yours when it was well-formed, otherwise a new one. Quote it to support.
The major API version (informational; the version is in the path).
More about this endpoint in the guide.