Skip to main content
GET
List monitorings

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
  • sort_direction (string, optional) - Sort order
    • Default: "desc"
    • Options:
      • "asc" - Ascending order
      • "desc" - Descending order
  • 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 objects
  • next_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:
  1. First request: Don’t include next_token
  2. Subsequent requests: Use the next_token from the previous response
  3. Last page: next_token will be null

Example Pagination Flow

Filter Behavior

  • Mutually Exclusive Filters: The website and state filters cannot be used together
  • Filter Precedence: If both filters are provided, website takes precedence and state is ignored
  • No Pagination with Filters: When using website or state filters, all matching results are returned and next_token is always null
  • Sorting with Filters: Sorting parameters (sort_by, sort_direction) are ignored when using filters

Notes

  • When filtering by website or state, 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

X-API-KEY
string
header
required

Query Parameters

page_size
integer
default:10

Number of items per page (1-100, default 10)

Required range: 1 <= x <= 100
sort_by
enum<string>
default:last_execution

Field to sort by (default: last_execution)

Available options:
last_execution,
next_run,
state,
website
sort_direction
enum<string>
default:desc

Sort order (asc or desc, default desc)

Available options:
asc,
desc
next_token
string

Pagination token for next page

state
string

Filter by running state

website
string

Filter by specific website URL

Response

OK

id
string<uuid>

Unique monitoring identifier

Example:

"d6e3b214-30b1-4401-a1b8-a1bd3c6a84e4"

website
string<uri>

The monitored website URL

Example:

"https://example.com"

customer_id
string

Customer identifier

checks
enum<string>[]

Active monitoring checks

Available options:
non_operational_website,
high_risk_diligent_classification,
catalog_contain_loan_flipping_indicators
frequency
enum<string>

Monitoring frequency

Available options:
weekly,
every_2_weeks,
every_3_weeks,
every_4_weeks
is_active
boolean

Whether monitoring is active

running_state
enum<string>

Current execution state

Available options:
IDLE,
RUNNING,
FAILED
next_run_at
string<date-time>

Next scheduled execution time

expires_at
string<date-time>

Monitoring expiration date

last_execution
string<date-time> | null

Timestamp of last execution, null if never executed

created_at
string<date-time>

Creation timestamp

updated_at
string<date-time>

Last update timestamp

execution_results
object[]

Results from the latest monitoring execution

external_id
string

External identifier for this monitoring