The Untether Labs API uses cursor-based pagination for most endpoints which return lists of items. This approach provides efficient and consistent navigation through result sets.Documentation Index
Fetch the complete documentation index at: https://developers.untetherlabs.com/llms.txt
Use this file to discover all available pages before exploring further.
Pagination Structure
All paginated endpoints return responses in the following format:Paginated Response Structure
Response Fields
An array containing the requested data items for the current page
A string token for fetching the next page, or
null if this is the last pageThe cursor value should be treated as an opaque string. The format is subject to
change without notice, clients should not attempt to decode or modify it.
Making Paginated Requests
Initial Request
Start by making a request to any paginated endpoint without a cursor parameter:Initial Paginated Request
Initial Response
Subsequent Requests
To fetch the next page, include the previous cursor value as a query parameter:Next Page Request
Last Page Detection
When you reach the last page, the cursor will benull:
Final Page Response
Best Practices
- Always treat cursor values as opaque strings
- Process items in batches rather than loading all pages at once for large datasets
- Consider implementing pagination limits in your application to avoid memory issues
Page counts are not currently provided in pagination responses. This may change
(per-endpoint) in the future.