Overview
Retrieve a paginated list of monitoring configurations for the authenticated customer. Supports filtering by website or state, and various sorting options.Request
- Method:
GET
- Path:
/monitorings
- Query Parameters: Optional filters and pagination
Query Parameters
page_size
(integer, optional) - Number of items per page- Default: 10
- Range: 1-100
- Must be a positive integer
sort_by
(string, optional) - Field to sort results by- Default:
"last_execution"
- Options:
"last_execution"
- Sort by last execution time"next_run"
- Sort by next scheduled run"state"
- Sort by running state"website"
- Sort by website URL
- Default:
sort_direction
(string, optional) - Sort order- Default:
"desc"
- Options:
"asc"
- Ascending order"desc"
- Descending order
- Default:
next_token
(string, optional) - Pagination token for next page- Base64 encoded token returned from previous response
- Used to fetch subsequent pages of results
state
(string, optional) - Filter by running state- Returns only monitorings in specified state
- Cannot be combined with website filter
website
(string, optional) - Filter by specific website- Returns only monitorings for the specified URL
- Cannot be combined with state filter
Example Request
Success Response
- Status: 200 OK
Response Body
items
(array) - List of monitoring objectsnext_token
(string|null) - Token for next page (null if no more pages)
Example Response
Error Handling
- 400 Bad Request
- Invalid query parameter values
- Example:
{ "error": "page_size must be a positive integer between 1 and 100" }
- 401 Unauthorized
- Missing or invalid customer authentication
- 500 Internal Server Error
- Unexpected server error
- Example:
{ "error": "Failed to fetch monitorings", "items": [], "next_token": null }
Pagination
The API uses cursor-based pagination with Base64-encoded tokens:- First request: Don’t include
next_token
- Subsequent requests: Use the
next_token
from the previous response - Last page:
next_token
will benull
Example Pagination Flow
Filter Behavior
- Mutually Exclusive Filters: The
website
andstate
filters cannot be used together - Filter Precedence: If both filters are provided,
website
takes precedence andstate
is ignored - No Pagination with Filters: When using
website
orstate
filters, all matching results are returned andnext_token
is alwaysnull
- Sorting with Filters: Sorting parameters (
sort_by
,sort_direction
) are ignored when using filters
Notes
- When filtering by
website
orstate
, pagination is not supported (returns all matching results) - The
next_token
is specific to the original query parameters and should not be reused with different filters - Invalid
next_token
values are ignored and treated as if no token was provided
Authorizations
Query Parameters
Number of items per page (1-100, default 10)
Required range:
1 <= x <= 100
Field to sort by (default: last_execution)
Available options:
last_execution
, next_run
, state
, website
Sort order (asc or desc, default desc)
Available options:
asc
, desc
Pagination token for next page
Filter by running state
Filter by specific website URL
Response
OK
Unique monitoring identifier
Example:
"d6e3b214-30b1-4401-a1b8-a1bd3c6a84e4"
The monitored website URL
Example:
"https://example.com"
Customer identifier
Active monitoring checks
Monitoring frequency
Available options:
weekly
, every_2_weeks
, every_3_weeks
, every_4_weeks
Whether monitoring is active
Current execution state
Available options:
IDLE
, RUNNING
, FAILED
Next scheduled execution time
Monitoring expiration date
Timestamp of last execution, null if never executed
Creation timestamp
Last update timestamp
Results from the latest monitoring execution
External identifier for this monitoring