/service/@id/uptime/monitorsList monitors
The account's monitors, filtered by state (state) and type (type), searched by name or target (q); cursor pagination (next_cursor). Each monitor has its latest state, last check, latency, open incident and 30-day uptime.
A Tino Uptime service route: call it with the service owner's sign-in token; the /v1 gateway (app tokens, personal tokens) does not expose Tino Uptime yet. See Getting started with Tino Uptime.
Authentication
Send the token in the header Authorization:
Authorization: Bearer <token>
Tokens that can call it: the Tino Uptime service owner's sign-in token (the tino.vn client area token).
Parameters
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
id | int | Required | Tino Uptime service ID |
Query
| Name | Type | Required | Description |
|---|---|---|---|
state | string | Optional | Filter by state: `pending`, `up`, `suspect`, `down`, `partial`, `down_international`, `paused` |
type | string | Optional | Filter by type (`settings.type`) |
q | string | Optional | Search the name or target, case-insensitive |
limit | int | Optional | Items per page, default 50, at most 100 |
cursor | string | Optional | `next_cursor` of the previous page; omit for the first page |
Response
Sample built from the Tino Uptime OpenAPI (Tino relays the answer as is inside data); values are examples.
Error codes
| Error code | Description |
|---|---|
404 · service_not_found, invalid method | The service does not belong to the signed-in account, or is not Tino Uptime. |
404 · service_not_linked | The service is no longer the customer's current Tino Uptime plan. |
403 · account_suspended | The Tino Uptime account is suspended: writes are blocked, GET still works. |
403 · entitlement_exceeded | Over a plan limit; details.resource names the limit. |
422 · validation_failed | Invalid data; details.field names the field. |
502 · network, invalid_response | The connection between Tino and Tino Uptime is interrupted: a Tino-side error, not a token problem. Retry later. |
Errors look like {"error": ["<CODE>"], "message", "details", "request_id"}; every code is in Getting started with Tino Uptime.