Documentation Index
Fetch the complete documentation index at: https://docs.arcuserp.com/llms.txt
Use this file to discover all available pages before exploring further.
Overview
All list endpoints in the Arcus API use cursor-based pagination. Unlike offset pagination (?page=3), cursor pagination is stable: inserting or deleting records between pages does not cause items to be skipped or duplicated.
List response envelope
Every list endpoint returns this envelope:| Field | Description |
|---|---|
object | Always "list" |
data | Array of resource objects for this page |
has_more | true if more pages exist after this one |
url | The endpoint URL for this list |
total_count | Total matching records (only when include_count=true is passed) |
Parameters
| Parameter | Type | Description |
|---|---|---|
limit | integer | Records per page. Default: 20. Max: 100. |
starting_after | string | Cursor: return records after this ID (exclusive). |
ending_before | string | Cursor: return records before this ID (exclusive). |
include_count | boolean | Include total_count in response. Adds a COUNT query; use sparingly on large tables. |
Paginating forward
Paginating backward
SDK usage: auto-pagination
All SDKs support automatic page iteration:Filtering and sorting
Most list endpoints support additional query parameters for filtering:Notes on performance
- Use
limit=100(the maximum) when bulk-fetching to minimize round trips - Avoid
include_count=trueon hot paths — it adds a COUNT query to every request - Cursors are stable: you can safely resume a paginated scan after an interruption by restarting from the last ID you successfully processed

