Competitor Price Monitoring API

kwery is a competitor price monitoring API for retail teams. Submit a list of GTINs or ASINs across Amazon, Google Shopping, eBay, Walmart, and 8 more sources. kwery fetches the current listing from each marketplace, validates price, Buy Box owner, seller count, and stock status, and returns a single GTIN-matched, normalized payload. Use it to feed a repricer, trigger alerts, or land data in your warehouse. One schema across every source. Fresh data on every request. No dashboard to maintain.

Competitor price monitoring is the practice of regularly tracking competitors' prices, stock levels, buy-box owners and promotions across the marketplaces where you sell. Retailers use it to feed repricing engines, protect MAP policies and alert their teams when meaningful market changes happen.

You send kwery a list of GTINs, ASINs or product URLs and specify the marketplaces you care about — Amazon, Google Shopping, eBay, Walmart, Idealo and 10+ more. For each request, kwery fetches the current listing from every marketplace, validates the fields and returns a single normalized payload with price, buy-box owner, seller count, stock, promos and shipping. You can call the endpoint synchronously or receive the response at a signed callback URL.

Those tools are closed dashboards with their own UI and workflow. kwery is API infrastructure. Use kwery when you already have a repricer, BI stack or alerting flow and need reliable, validated data to feed it — without paying for a UI you won't use.

Yes. Every response includes seller identity and price, so you can filter for unauthorized sellers or prices below your MAP floor and route those into a dedicated queue.

Every request triggers a fresh fetch from the marketplace at the moment you call kwery. Freshness is measured from your request, not from an internal poll — so you always get the current listing as the marketplace shows it.

Yes. Every response includes the current buy-box owner, seller count, stock status, promo flags and shipping cost alongside the price.

Yes. Most teams call kwery on a cadence that fits their SKU tier (e.g. hourly for hot SKUs, daily for the long tail), diff the response against their last stored value, and route only meaningful deltas — e.g. `delta_pct > 1%` or `buy_box_seller` changed — into their repricer or alerting.

Point your ingestion pipeline at the kwery response — either poll our endpoint on your schedule or receive it at your callback URL. The payload is stable, signed with HMAC and idempotent — safe to retry, safe to fan out to multiple consumers.