Pagination
List endpoints that return collections use cursor pagination where noted. There is no page-number pagination on the public v1 API.
Changes
GET /v1/changes returns:
| Field | Type | Description |
|---|---|---|
changes |
array | Result page |
has_more |
boolean | More results available |
next_cursor |
integer \ | null |
Example
First page:
curl "https://api.competiflow.com/v1/changes?workspace_id=42&limit=25" \
-H "Authorization: Bearer $COMPETIFLOW_API_KEY"
Next page (when has_more is true):
curl "https://api.competiflow.com/v1/changes?workspace_id=42&limit=25&after=900" \
-H "Authorization: Bearer $COMPETIFLOW_API_KEY"
The cursor is opaque: always use the next_cursor value from the previous response. Do not assume sequential IDs alone define order.
Other list endpoints
| Endpoint | Pagination |
|---|---|
GET /workspaces |
Returns all workspaces (typically small) |
GET /workspaces/:id/competitors |
Returns all competitors in workspace |
GET /monitors |
Returns all matching monitors |
If these grow large in the future, cursor params will be documented here first.