Syncing Data

Several list endpoints support an updated_since filter, making it easy to build incremental sync pipelines that only fetch what's changed.

Incremental Sync Pattern

1. On the first sync, fetch all records (paginate through the full dataset)
2. Store the timestamp of when you started the sync
3. On subsequent syncs, pass ?updated_since=LAST_SYNC_TIMESTAMP to only fetch records modified since your last run
4. Paginate through results until next_cursor is null

Code
 
# Initial sync
curl "https://api.datavisual.ca/v1/items?limit=200" -H "Authorization: Bearer KEY"

# Subsequent syncs — only records changed since last run
curl "https://api.datavisual.ca/v1/items?limit=200&updated_since=2025-01-15T00:00:00Z" \
  -H "Authorization: Bearer KEY"

Supported Endpoints

created_after is useful for "orders placed since" workflows where you care about creation time rather than last modification.

The following endpoints do not support updated_since:

• /v1/account and /v1/account/addresses — these return your current account snapshot, not a historical list
• /v1/stock and /v1/warehouses — fetch the full dataset each time

Recommendations

• Sync frequency: Poll every 5–15 minutes for most use cases. Use webhooks (coming soon) for real-time needs.
• Overlap your timestamps: Use a small overlap (e.g., subtract 1 minute from your last sync time) to avoid missing records changed during the previous sync.
• Handle pagination fully: Always paginate through all pages before considering a sync complete.
• Use expand sparingly during sync: Expansions increase response size. Fetch expanded data only for records you need to process in detail.