Pagination and incremental sync

List endpoints use opaque cursor pagination.

Parameters

| Parameter | Type | Default | Description | | --- | --- | --- | --- | | limit | integer | 100 | Records evaluated per page; minimum 1, maximum 250 | | cursor | string | none | nextCursor from the previous response |

curl "https://api.spoolrule.com/inventory/items?limit=250&cursor=eyJpdGVtSWQiOiJpdG1fLi4uIn0" \
  --header "Authorization: Bearer $COILINX_API_KEY"

Continue until meta.hasMore is false. A page can contain fewer than limit records because filters are evaluated by the datastore.

Cursor rules

• Treat cursors as opaque.
• Do not decode, modify, persist indefinitely, or reuse a cursor with different filters.
• Restart the listing if a cursor returns 400.
• De-duplicate by Coilinx resource ID when a dataset changes during traversal.

Incremental item synchronization

After the initial pull, store a high-water timestamp. Request:

GET /inventory/items?updatedSince=2026-07-14T15:00:00Z

Use a small overlap (for example, five minutes), de-duplicate by item ID, and advance the high-water mark only after every page is committed successfully. This protects against clock skew and interrupted jobs.

Webhooks provide faster notification, but periodic updatedSince reconciliation remains recommended to recover from delivery failures.