One API. Every Marketplace, Normalized.

Twelve sources today: Amazon, Google Shopping, ebay, Idealo, Kaufland, Otto, billiger.de, guenstiger.de, Walmart, Lidl, AliExpress, and Rakuten. Each one has its own page in the Source Library with the identifiers it accepts and the countries it covers. View Source Library.

Short identifiers: amazon, google, ebay, idealo, kaufland, otto, billiger, guenstiger, lidl, walmart, rakuten, aliexpress. Display names such as google_shopping return "unknown source". Source identifiers in the docs.

Yes. You specify which sources a job should cover, and results come back per source in the same response schema, so comparing an Amazon observation with an Idealo one needs no source-specific handling.

Lookups run as jobs. You submit a batch of identifiers, kwery resolves each one against the live marketplace, and results stream back as batches complete rather than blocking a single long request. Small jobs finish quickly; large jobs deliver progressively. For a single lookup, wait returns the result in the same response (up to 120 s). If it takes longer, you get a job ID to poll instead. Batches always run as jobs.

Provide a callback_url when you submit a job and results are delivered to it as JSON. Webhooks are signed so you can verify authenticity, retried automatically on failure, and replayable on demand if your endpoint was down. Webhook delivery.

Yes, with two per-job parameters. max_age (seconds, default 1200) sets how old a cached observation may be before kwery fetches again; set it to 0 to force a live fetch every time. not_found_max_age (days, default 10) sets how long a cached "not found" is honoured before the next check re-crawls. Anything answered from cache is free, so widening the windows lowers your credit consumption. Data quality details.

A successful result is billed. A freshly crawled "not found" is billed too, because we still did the work of checking. A "not found" re-served from the not-found cache, and any failed request, cost nothing. For most sources 1 credit delivers a full data set for one SKU. On Amazon, Walmart, and eBay, 1 credit delivers 2 full data sets (search + product + offers, matched, each). Kaufland costs 3 credits per result, reflecting its higher delivery cost. Pricing overview.

You get an explicit not-found result rather than an empty or guessed record. That answer is cached for 10 days by default (adjustable per request with not_found_max_age), and re-checks inside that window are served from cache and cost 0 credits. After the window expires, the next check triggers a fresh crawl, which is billed at the source's normal credit rate. Pricing and credits.

"not found" means the marketplace does not know the product. A product with no purchasable offer right now is a normal result with offers_count 0 and buybox null. Per-result fields in the docs.

A contractual SLA, 99.9% uptime with service credits, defined response times, and per-source freshness targets, is part of the Enterprise tier and documented in your agreement. Every plan, including free and Growth, runs on the same infrastructure with signed webhooks, automatic retries, replay on demand, and public service-health signals, but without a contractual uptime commitment.