Pagination
Most list endpoints use page‑based pagination:| Parameter | Type | Default | Max | Description |
|---|---|---|---|---|
page | integer | 1 | — | 1‑based page number. |
limit | integer | 15 | 100 | Number of items per page. |
page and limit, and includes total for building pagination controls or iterating until exhausted:
Cost Estimations use offset‑based pagination instead, with
limit (default 50, max 100) and offset (default 0). This is called out explicitly on the List Cost Estimations page.Sorting
Endpoints that support sorting accept two parameters:| Parameter | Type | Description |
|---|---|---|
sort_by | enum | Which field to sort by. Valid values vary per endpoint. |
sort_order | enum | ASC or DESC. Defaults to DESC. |
sort_by values are documented on each list endpoint. Examples:
- List scans:
created_at,updated_at,status - List findings:
found_at,updated_at,severity
sort_by is omitted, the endpoint-specific default applies (see each list page).
Filtering
Filters are passed as additional query parameters. Each list endpoint documents the filters it supports. The patterns below are shared across list endpoints.Enum filters
Enum filters accept the canonical lower‑snake‑case value and return only records that match:Scoped filters
Some filters restrict results to a related resource:404 is returned if the resource does not exist or is not visible to the key.