Your data, served through an API you control.
Files suit analysts; applications need endpoints. We expose your datasets through a dedicated REST API and webhooks, or sync them straight into your warehouse, with authentication, rate limits and versioned schemas that keep integrations stable.
Engineering teams waste time parsing emailed files, handling inconsistent column names and rebuilding integrations each time a supplier changes format. Without a stable interface, scraped data is hard to use inside live products and pricing engines.
Your systems query or receive data through a documented contract that does not change without notice. New fields arrive in new schema versions, old versions stay available during migration, and access is controlled per key.
Everything needed to run it in production.
Dedicated REST endpoints
Query datasets by entity, source, market or date range, with filtering, pagination and consistent JSON responses.
Webhooks
Push notifications for new deliveries or change events, signed so your systems can verify they came from us.
Authentication and access control
API keys or OAuth client credentials, scoped per dataset and environment, with key rotation on request.
Rate limits and quotas
Documented request limits per key, with headers that show remaining quota so clients can back off gracefully.
Schema versioning
Breaking changes ship as a new version, with deprecation notices and a parallel-run period for the old one.
Warehouse and storage sync
Scheduled loads into your cloud data warehouse, or drops to cloud storage buckets and SFTP, alongside the API.
What lands in your systems.
| endpoint | method | schema_version | auth | rate_limit | returns | market_filter |
|---|---|---|---|---|---|---|
| /v2/prices | GET | 2.3 | API key | 600/min | Latest price per SKU and source | AE, SA, SG, GB |
| /v2/prices/history | GET | 2.3 | API key | 120/min | Daily price history, up to 24 months | AE, SA, SG, GB |
| /v2/stock | GET | 2.1 | OAuth client | 600/min | In-stock status by store or zone | AE, QA, KW |
| /v1/deliveries | GET | 1.4 | API key | 60/min | Delivery manifest with file links | All |
| webhook: price.changed | POST | 2.3 | HMAC signature | n/a | Change event with old and new value | BR, MX |
Illustrative rows. Your schema, field names and formats are agreed during scoping.
Who uses it, and for what.
Repricing engines call the prices endpoint directly rather than importing files. Webhooks trigger recalculation only when a competitor actually moves.
Feature pipelines load daily snapshots into the warehouse on a fixed schedule. Versioned schemas mean model code does not break unexpectedly.
Internal tools and CRM integrations query stock and listing status on demand. Account managers see current data without exporting spreadsheets.
Controllers receive a delivery manifest with file hashes and row counts for reconciliation. Audit trails show what was delivered and when.
- Scope. Tell us the sources, fields and frequency. We confirm feasibility within a day.
- Free sample. A real sample from your own target source, in your format.
- Build. Engineers build extractors tuned to each source. No generic templates.
- Validate. Automated and manual QA on every run before anything ships.
- Deliver and monitor. Scheduled delivery, monitored pipelines, fast fixes when sites change.
Related services
Industries that use it
How are breaking changes handled?
Breaking changes are released under a new schema version with advance notice. The previous version keeps running for an agreed overlap period so you can migrate on your own timeline.
What authentication do you support?
API keys and OAuth client credentials are standard, scoped per dataset and environment. Webhooks are signed with HMAC so your receiver can verify the sender.
Can we use the API and still get files?
Yes. Many clients use the API for applications and a scheduled warehouse load or file drop for analytics. Both are served from the same validated dataset.
What are the rate limits?
Limits are set per key according to your use case and documented with the endpoint. Response headers show remaining quota, and limits can be raised if your usage grows.