Integration & Delivery

    How teams authenticate, consume webhooks, handle rate limits, and integrate kwery with their existing data and pricing stack.

    Integration10 Questions

    kwery uses API keys scoped to your organization. Keys can be rotated and scoped per environment so staging and production never share credentials. API documentation.

    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.

    Limits depend on your plan and source. Direct API plans are sized to your real traffic profile during onboarding; self-serve access uses published per-tier limits. There is no hard cap on job size — submit 1,000 GTINs or 10 million, and results stream back as batches complete.

    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 with exponential backoff over several hours. After the final attempt, the event is held for manual replay rather than dropped.

    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.

    Still Have Questions?

    Request API access and the team will walk through sources, volumes, and integration in detail.

    Free Tier Available
    Enterprise SLA (99.9% Uptime)
    Global Scale