Pagination

GET list endpoints currently return at most 100 records, ordered by most recent first. There is no cursor or offset parameter today.

Implications

• List endpoints are not sync-safe. A tenant with 300 orders cannot enumerate all of them through GET /orders/. Do not use list endpoints as a sync source.
• Ordering is newest-first for Orders and Inventory. For Locations and Products it's insertion order filtered by is_active=true.
• No totals. The response has no count, total, or next link.

What to use instead

Goal	Do this
Verify a record you just created	GET /orders/{identifier}/ — direct lookup is always correct
Pull all current inventory for a loc	GET /inventory/{location_code}/ — returns all rows for that location
Full reconciliation	Coming via export jobs / webhooks. Contact support for the current option for your tenant.

What's coming

Cursor pagination (?cursor=, next_cursor in response) is on the roadmap for all list endpoints. Once available, existing clients will continue to work — the cap will increase to 500 per page and next_cursor will be returned when more data exists.

See Versioning for how new fields are added without breaking existing clients.