Price Tracking API

    One REST endpoint, a stable versioned schema, HMAC-signed webhooks on change. Built to plug into repricers, feed engines and data platforms — not into a dashboard you'll never open.

    12+ Sources, One Endpoint · REST API with Change Webhooks

    What You Get

    Everything You Need. Nothing You Don't.

    01API design

    Versioned, predictable schema

    Every response follows one versioned contract per resource. Fields don't shift under you — old clients keep working, new fields land additively.

    02Delivery

    REST in, webhook out

    Poll on your schedule or subscribe an SKU to change detection and receive an HMAC-signed POST when price, stock or Buy Box actually moves.

    03Cost model

    Per-request, no seats

    You pay for successful requests. No seat fees, no annual commit, no minimum. Prototype on the free tier before you talk to anyone.

    How It Works

    REST in. JSON out. Webhook on change.

    kwery exposes one REST endpoint per resource, a stable response schema, and change-detection webhooks. Point your ingestion pipeline at it and stop maintaining scrapers.

    1. POST your query

      One endpoint, one request shape, one response schema across all 12+ sources — no per-marketplace adapter layer in your codebase.

    2. Live fetch across sources

      Payloads are idempotent and signed with HMAC, safe to retry and safe to fan out to multiple downstream consumers.

    3. JSON or signed webhook

      Rate limits, credits remaining and next-reset time are returned on every response header so your client can back off gracefully.

    POST · api.kwery.co/stream
    {
      "job_id": "pt_92fa14c...",
      "status": "finished",
      "results": [{
        "updated_at": "2026-06-27T11:31:09.731Z",
        "query": {
          "source": "amazon",
          "country": "us",
          "topic": "search_and_offers",
          "key": "asin",
          "value": "B08N5WRWNW"
        },
        "content": {
          "asin": "B08N5WRWNW",
          "title": "Echo Dot (4th Gen) Smart Speaker with Alexa",
          "brand": "Amazon",
          "category": "Smart Speakers",
          "country": "us",
          "currency": "USD",
          "price": 49.99,
          "bbx_price": 49.99,
          "shipping": 0,
          "buybox_owner": "Amazon.com",
          "seller_type": "FBA",
          "no_sellers": 14,
          "is_available": true,
          "review_rating": 4.7,
          "review_count": 412037,
          "offers_count": 14,
          "offers": [
            {
              "price": 49.99,
              "currency": "USD",
              "condition": "new",
              "shop_name": "Amazon.com",
              "shop_review_rating": 4.9,
              "shop_review_count": 1842301
            }
          ]
        },
        "success": true
      }]
    }

    What the API Exposes

    The Primitives You'll Actually Build On.

    Versioned response contract

    One schema per resource, semantically versioned. Fields are added, never quietly renamed under working clients.

    Schema

    Price & effective price

    List price, effective price and prior value — enough surface for your diff logic to fire on meaningful moves only.

    Price

    Buy Box / top offer

    Consistent `buybox_owner` and `seller_type` fields across sources so repricer logic doesn't fork per marketplace.

    Winner

    Availability signals

    In-stock, out-of-stock and low-inventory flags per SKU and seller — the states that gate a real purchase.

    State

    HMAC-signed webhooks

    Subscribe SKUs and receive signed POSTs on change. Retry-with-backoff and signature verification are built in.

    Events

    Warehouse-friendly payloads

    Idempotent, safe to fan out to BigQuery, Snowflake or your data lake without duplicate-row logic.

    Sink

    Who Ships With This

    Engineering Teams Building Pricing Infrastructure.

    Use case01

    Repricer engineering

    Skip the scrapers, proxy pools and parser drift. Build against a stable schema and spend your cycles on pricing logic.

    Feeds → repricer service

    Use case02

    SRE / observability

    Wire change-detection webhooks into your alerting so on-call gets paged on real market moves, not on polling noise.

    Feeds → PagerDuty / Slack

    Use case03

    Data platform teams

    Land idempotent payloads directly in BigQuery or Snowflake. Backfill without dedup headaches; expose to analysts through your existing models.

    Feeds → warehouse tables

    Self-Serve

    One Credit. One Resolved SKU

    Product matching, product page, and offers — billed as a single credit.

    01

    Product Matching

    Identify the correct product within the requested source using GTIN or URL.

    02

    Product Page

    Title, brand, specs, images, and category — fully normalized.

    03

    Offers

    Every seller, price, condition, and shipping option in the offer section.

    Entry Price

    €399 / mo

    Included

    100k credits / mo

    Overage

    €3.99 / 1k credits

    Support

    Common Questions

    What most teams want to know before integrating kwery.

    Browse all FAQs

    kwery is a price tracking API across 12 sources — Amazon, Google Shopping, eBay, Walmart, Idealo, and more. Submit a list of GTINs or ASINs, and kwery resolves each listing by GTIN match, validates price and stock, and returns one normalized payload with full audit provenance. Use it to feed a repricer, power alerts, or land data straight in your warehouse. One schema, every request fresh.

    12+ sources including Amazon, Google Shopping, eBay, Walmart, Idealo, Otto, Kaufland, Billiger and Lidl. The response schema is the same across all of them — one integration in your code.

    Each resource has a semantic version. Additive changes ship without a bump; renames and removals ship as a new major version pinned via header. Old clients keep working; upgrading is opt-in.

    Node / TypeScript is the primary SDK. Python is in beta. Any HTTP client works against the REST endpoints directly — the docs include cURL examples for every route.

    Every response includes `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Reset` headers. Back off gracefully by reading them; there's no need to model your own quota separately.

    Each POST is signed with HMAC-SHA256 using your endpoint's secret. Verify the signature header before trusting the body. Retries follow exponential backoff until your endpoint returns 2xx.

    Enough successful requests to prototype against your data model without a credit card. Upgrade only when you're ready to send production traffic.

    Paid plans include a 99.9% uptime SLA with credits for downtime. Enterprise plans layer custom SLAs, dedicated capacity and named support on top.

    Build Against a Schema That Won't Move Under You.

    REST, versioned JSON, signed webhooks. Prototype on the free tier and only pay when it's serving real traffic.

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