Pagination

All list endpoints use cursor pagination:

curl "https://api.nembol.com/rest/v1/products?limit=50" \
  -H "Authorization: Bearer $NEMBOL_API_KEY"

{
  "data": [ { "id": "…" } ],
  "has_more": true,
  "next_cursor": "eyJ1IjoiMjAyNi0wNy0yNFQx…"
}

Pass next_cursor back as ?cursor= to get the next page. When has_more is false, you're done. limit is 1–100 (default 25). Cursors are opaque — don't parse or store them long-term.

Ordering guarantee

Lists are ordered by updated_at descending with a stable id tiebreak. This order is part of the contract — pages never skip or repeat items within a single crawl.

Incremental sync

To keep an external system in sync without re-reading everything, crawl with updated_after:

curl "https://api.nembol.com/rest/v1/products?updated_after=2026-07-24T00:00:00Z&limit=100" \
  -H "Authorization: Bearer $NEMBOL_API_KEY"

Record the timestamp you started the crawl at, page through to the end, then use that timestamp as the next crawl's updated_after. (For push-based sync, use webhooks instead — crawling is the reconciliation fallback.)