Pagination
The Collate API uses cursor-based pagination for list endpoints. This ensures consistent results even when data changes between requests.How It Works
Pagination Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
limit | integer | 10 | Number of results per page (max 1000) |
before | string | - | Cursor for previous page |
after | string | - | Cursor for next page |
Response Fields
Thepaging object contains:
| Field | Type | Description |
|---|---|---|
total | integer | Total count of matching resources |
before | string | Cursor for the previous page (if available) |
after | string | Cursor for the next page (if available) |
Examples
Basic Pagination
Basic Pagination
Iterating Through All Results
Iterating Results
Filtering with Pagination
Combine pagination with filters for efficient data retrieval:Filtering
Include Fields
Control which fields are returned in the response using thefields parameter:
owner- Include owner informationtags- Include tags and classificationscolumns- Include column definitionsfollowers- Include followerstableConstraints- Include constraintsusageSummary- Include usage statistics
Best Practices
Use reasonable page sizes
Start with
limit=50-100. Larger pages reduce API calls but increase memory usage.Request only needed fields
Use the
fields parameter to reduce response size and improve performance.Pagination vs Search
For finding specific resources, consider using the Search API instead of paginating through all results:Search API
Learn about searching and filtering metadata