Use whichever fits your workflow. Webhooks work best for large jobs (1.000+ products) where you want results as they complete, no polling loops, cleaner architecture. Polling is simpler for smaller jobs or when you prefer to pull on your schedule. Both use the same underlying API and pricing. Webhooks reference.
Yes. kwery is API-first and emits structured JSON, so you can land events directly in a warehouse, feed them into a custom pricing engine, or route them through your existing ETL. Architecture and integration model.
Webhooks guarantee at-least-once delivery, so the same event may arrive more than once. Every event carries a signed payload and an idempotency key, deduplicate on that key before processing. Webhooks reference.
Any delivery can be replayed on demand from the dashboard or API. Combined with retries, no validated change is lost, you can backfill the window you missed without re-running jobs.
Every webhook payload is signed with HMAC-SHA256 using a shared secret bound to your endpoint. Verify the signature header before processing to confirm the payload came from kwery and was not tampered with.
Failed deliveries are retried automatically, 5 attempts on an immediate, +30 s, +2 min, +10 min, +30 min schedule with 20% jitter, so roughly 45 minutes end to end. Only 3xx, 5xx, 429 and network errors are retried; any other 4xx is treated as a permanent failure. After the final attempt the delivery is dead-lettered, not lost, it can be replayed from the dashboard, and results stay downloadable for 3 days.
kwery retries automatically, 5 attempts over roughly 45 minutes if your endpoint doesn't acknowledge the delivery. Only 3xx, 5xx, 429 and network errors are retried; any other 4xx is treated as a permanent failure. Every payload carries a batch sequence and timestamp, so even if a retry arrives out of order, you can reconcile it against your own records. After the final attempt the delivery is dead-lettered rather than dropped: it can be replayed from the dashboard, and results stay downloadable for 3 days. You can also switch a source between webhook and polling delivery at any time without losing historical data. Webhooks reference.
Most teams are live within a few days. You authenticate, point a webhook or polling job at the endpoints you need, and start receiving normalized JSON.
No. kwery is the data layer underneath whatever pricing logic you already run. Your ERP, PIM, repricer, or custom engine keeps full control. We only deliver the marketplace data they consume.
Compare buybox.seller_id in each Amazon result with your own seller ID. When a later check detects a change in Buy Box ownership, kwery can deliver the updated result to your signed webhook so your pricing logic can decide how to respond. Webhooks reference.
Request API access and the team will walk through sources, volumes, and integration in detail.