Incremental Sync
Learn how to efficiently keep your Okasie listings in sync with your inventory system using incremental updates.
Why Incremental Sync?
Instead of uploading your entire inventory every time, incremental sync allows you to:
- Reduce API calls - Only sync what changed
- Faster updates - Changes appear on Okasie within seconds
- Lower bandwidth - Send only the delta
- Stay within rate limits - Avoid hitting 120 req/min limits
Sync Strategies
1. Timestamp-Based Sync (Recommended)
Use the updatedSince parameter to fetch only listings changed since your last sync.
2. Full Inventory Comparison
For systems without change tracking, compare full inventories:
When fetching listings, always handle pagination:
Batch Updates with Bulk Upsert
For efficiency, always use the bulk upsert endpoint:
Change Detection
Implement smart change detection to avoid unnecessary updates:
Handling Deletions
When a car is sold or removed from your inventory:
Scheduling Recommendations
Error Recovery
Implement retry logic with exponential backoff:
Store the updatedAt timestamp from each listing to detect changes on both sides. This enables true bi-directional sync if needed.