Updated Jul 14, 2026
On this page

Incremental Sync

Avoid re-fetching the full dataset on every run. Use ?updated_since= for delta sync.

Flow

  1. Initial full sync: GET /api/v1/slots/ (paginate through all pages).
  2. Store the X-Sync-Timestamp response header value.
  3. Next run: GET /api/v1/slots/?updated_since=<stored-timestamp> — only changed items.
  4. Update your stored timestamp from the new X-Sync-Timestamp.
curl -H "Authorization: Token <YOUR_TOKEN>" \
  "https://i-gaming.tools/api/v1/slots/?updated_since=2026-01-01T00:00:00Z"

ETag / 304 Not Modified

For single-resource endpoints, send If-None-Match with the stored ETag. A 304 response means the resource is unchanged; your quota is still decremented.

Tombstone reconcile via /ids/

Items unpublished between syncs do not appear in delta results. Use GET /api/v1/slots/ids/ to get the full set of current IDs and diff against your local set.

See Conventions for timestamp format details.