Every list endpoint in the Spotzee API uses cursor pagination. Cursors are stable across inserts and deletes, so you never miss or duplicate a record while paging.Documentation Index
Fetch the complete documentation index at: https://docs.spotzee.com/llms.txt
Use this file to discover all available pages before exploring further.
Request parameters
| Parameter | Default | Notes |
|---|---|---|
limit | 25 | 1 – 100 inclusive |
cursor | none | Opaque cursor returned by a previous page |
direction | forward | forward (older → newer) or backward |
sort | endpoint-specific | Field to sort on. Prefix with - for descending, e.g. -created_at |
q | none | Free-text search where the endpoint supports it |
Response shape
| Field | Meaning |
|---|---|
results | The records on this page |
nextCursor | Cursor for the next page; null when you’ve reached the end |
prevCursor | Cursor for the previous page; null on the first page |
limit | Echoes the limit you asked for |
has_more is derivable: it’s nextCursor !== null.
Response headers
For convenience, list endpoints also emit:| Header | Meaning |
|---|---|
X-Total-Count | Total records that match the query (best-effort; large collections may return an estimate) |
X-Page | Page index when one is meaningful |
X-Limit | Echoes the limit query parameter |
Walking a list
Sort
Passsort as a single field name. Prefix with - for descending order:
400 parameter_invalid_format.
Filtering
Use simple?key=value filters where supported. The fielded query language (AIP-160 syntax) is on the roadmap.
Limits in practice
- Use
limit=100for bulk processing — fewer round-trips, predictable headers. - Use
limit=25(the default) for interactive UIs. - Going above
100returns400 parameter_invalid_format.
Next steps
Rate limits
Stay under your per-second budget while paging.
Errors
Status codes and the
code catalogue.