One API. Every Marketplace, Normalized.
Designed for production
Catalog Modeling
Catalog-Scale Price Delivery
Stop designing complex request logic. Model your catalog and kwery handles the heavy lifting.
Map by GTIN/EAN
Track SKUs across the web using standard identifiers, not just brittle URLs.
Define Frequency
Set refresh rates tailored to your strategy, from daily snapshots to real-time updates.
Global Routing
Access multiple marketplaces through one endpoint without managing individual scrapers.
GTINs/EANs
Marketplaces
From Requests to Credits
Now that you know how kwery resolves your catalog, here's what it costs.
Each resolved SKU-source fetch consumes one credit. Failed lookups and cache hits are always free.
See full pricingWorkflow
From Request to Result
Three steps to production-grade marketplace data.
Create a Job
Post a batch of product identifiers to the unified /sessions endpoint. No manual queue management required.
Processing
kwery resolves proxies, bypasses bot-detection, and normalizes all source-specific fields in real-time.
Retrieve Signals
Poll the job ID or receive an automated Webhook once the normalized result is stored in our high-speed cache.
Source Library
Full Coverage, One Endpoint
Pricing, offers, and merchant data from the marketplaces that drive your category, delivered through a single normalized API.
On-Demand
Don't See Your Marketplace?
Request a new source and we'll integrate it into the API, zero downtime, unified schema.
Technical Specs
Full-Spectrum Pricing Data
Every source returns the same normalized schema, offer lifecycle, logistics, market signals, and compliance. Sample responses across three sources.
Tap a category to highlight in the response →
{"asin": "B01N5N6RSS","buybox_price": 550.96,"currency": "EUR","seller_type": "FBA","buybox_owner": "sr_versandhaus","buybox_owner_id": "A1B2C3D4E5","is_available": true,"review_rating": "4.7 of 5","review_count": 1242}
Universal Search Keys
Query via GTIN, EAN, ASIN, PZN, search terms, or direct marketplace URLs. Our routing layer maps identifiers to local product entities instantly.
Control Parameters
Customize crawl depth with max_pages or enforce strict data freshness with max_age parameters for real-time validation.
Connectivity
Engineered for Integration
kwery is a versioned API built for system-to-system reliability, not a simple scraper wrapper.
Delivery Formats
Format negotiationNative JSON support (recommended) with CSV and custom formats available upon request for legacy data pipelines.
Versioned Schema
Code stabilityGuaranteed code stability. All job results are stored and available for retrieval for 72 hours via versioned endpoints.
Event-Driven
WebhooksInstead of constant polling, receive a POST request the moment your data is resolved into our persistent result storage.
Predictable Billing
Per-creditPer-credit pricing tied to resolved SKUs. Failed lookups and cache hits within max_age cost zero credits.
Going Deeper
What Is a Marketplace Data API, Exactly?
See how collection, normalization, matching, and delivery fit together.
Reliability
Architected for Scale
Always-on pricing infrastructure for enterprise catalog refreshes.
High-Frequency Refresh
Continuous checks at scale. Configurable refresh rates, from daily snapshots to real-time, keep your catalog current, while detected change events surface exactly what moved between observations.
Enterprise Uptime SLA
99.9% uptime SLA, contractually guaranteed for Enterprise customers. Every tier runs on the same redundant infrastructure just without guarantees and commitments.
Explicit Error Taxonomy
Granular visibility into request behavior with specific error codes for missing parameters and source health alerts.
HTTP 503: SOURCE_TIMEOUT
Support
Common Technical
Questions
Detailed answers covering integration, data quality, volume, and compliance. Full answers live in the knowledgebase.
Browse all FAQskwery provides three layers of defensibility: audit trails (every observation includes timestamp and source attribution), confidence scores (document which results you filtered and why), and signed change events (your repricing reacts to actual market movement, not noise). Together this gives compliance teams a clear record of how each pricing decision was reached using market data, not personal consumer data. Compliance & Provenance.
When a source updates its site, schema, or listing behavior, kwery absorbs the change centrally and keeps your integration stable. Your pipeline keeps receiving normalized results in the same schema, no code changes on your side. Brief gaps are surfaced as explicit health signals, never as stale data.
Every result is resolved live from the marketplace, not pulled from a static or aggregated feed, even inside a large batch job, each SKU is fetched at the moment it's actually processed, not pre-fetched from a snapshot taken when the job started. Every record carries an observed_at timestamp, and you control exactly how fresh you need it with the max_age parameter (in seconds, default 1200/20 minutes, maximum 259200/3 days): set it to 0 for a guaranteed live fetch every time, or allow a window so a request doesn't trigger a redundant fetch when nothing's likely to have changed. Learn more about our data quality.
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.
Plans are scoped by sources, request volume, and delivery model (pull, webhook, stream). Self-serve tiers have published per-credit pricing; Direct API plans are sized to your real usage during onboarding. Pricing overview.
Start Building on kwery
Self-serve API keys after signup. Enterprise volume, SLAs, and dedicated support available on request.