All list endpoints in the Ruddr API use cursor-based pagination. Results are sorted in reverse chronological order (newest first).
List endpoints return a wrapper object:
{
"results": [
{ "id": "...", "createdAt": "2024-01-15T10:30:00.000Z", ... },
{ "id": "...", "createdAt": "2024-01-14T09:00:00.000Z", ... }
],
"hasMore": true
}
| Field | Type | Description |
|---|
results | array | Array of resource objects |
hasMore | boolean | Whether additional pages exist in the traversal direction |
Query Parameters
| Parameter | Type | Default | Description |
|---|
startingAfter | UUID | — | Cursor ID from the previous response to request the next page |
endingBefore | UUID | — | Cursor ID from the previous response to request the previous page |
limit | integer | 10 | Maximum number of results to return (1–100) |
startingAfter and endingBefore are mutually exclusive — only one can be used per request. Omitting both returns
results from the beginning.
Iterating Through Pages
To fetch all results, use the id of the last item in each response as the startingAfter cursor for the next request. Continue until hasMore is false.
Example
First page:
curl "https://www.ruddr.io/api/workspace/clients?limit=10" \
-H "Authorization: Bearer YOUR_API_KEY"
Next page (using the last id from the previous response):
curl "https://www.ruddr.io/api/workspace/clients?limit=10&startingAfter=LAST_ID" \
-H "Authorization: Bearer YOUR_API_KEY"
Previous page (using the first id from the current response):
curl "https://www.ruddr.io/api/workspace/clients?limit=10&endingBefore=FIRST_ID" \
-H "Authorization: Bearer YOUR_API_KEY"