Updated September 2026

    Traject Data vs kwery

    Traject Data offers specialized APIs for individual marketplaces. kwery covers supported marketplaces through one API with consistent fields, product matching, data-quality context and provenance.

    Get API KeyCompare

    What Traject Data Is Known For

    Traject Data offers a family of per-marketplace APIs, Rainforest for Amazon, BlueCart for Walmart, Countdown for eBay, RedCircle for Target and BigBox for Home Depot, each with its own response shape. kwery covers 12 marketplaces behind one endpoint and one schema, so adding a marketplace does not mean adding another integration.

    A portfolio of dedicated source APIs, including Rainforest API for Amazon, plus Walmart, eBay, Target and Home Depot, each modelled closely on its own source.

    01

    Source-Specialized APIs

    Separate APIs per source, including Rainforest API for Amazon and dedicated Walmart, eBay, Target and Home Depot products.

    02

    Amazon Request Depth

    Rainforest API exposes distinct Amazon request types for product, offers, reviews, search and category surfaces.

    03

    Source-Native Fields

    Responses stay close to the source model, so marketplace-specific detail is not flattened away.

    04

    US Retail Breadth

    Strong coverage of large US retail sources across the portfolio.

    Where the Products Overlap

    A fair comparison starts with the shared ground. Both products are used for the following, which is why they appear in the same evaluation at all. Below the shared band, the ledger shows where the two designs diverge.

    Shared capabilities between Traject Data and kwery, and the dimensions where the two designs diverge.

    Where they overlap

    current product, price and offer data from major marketplaceslookups by marketplace identifier or source URLdetailed offer and seller informationuse inside monitoring, repricing and analytics workflows

    Where they diverge

    01

    Relevant source coverage

    Traject Data

    Strong US retail portfolio, one API per source

    kwery

    European and global marketplace library behind one API

    02

    How much detail per source

    Traject Data

    High per source; Amazon depth is a particular strength

    kwery

    Direct collection with marketplace seller, shipping and availability preserved

    03

    Finding the right product

    Traject Data

    You supply the source's own identifier (ASIN, item ID) or a URL; barcodes are not supported

    kwery

    Barcode or marketplace ID resolved to the product on that marketplace, with a match confidence returned

    04

    Same fields across sources

    Traject Data

    Your application maps each source's field names

    kwery

    Every source returns the same fields

    05

    Can you trust the data?

    Traject Data

    Not offered, you get a response status, not a confidence signal

    kwery

    A trust score and data-health flags come back with every record

    One API per Marketplace or One API for All of Them?

    A per-source API can be the better tool when one marketplace dominates the requirement. Nothing is abstracted away, the request types mirror the source, and the response reflects exactly how that marketplace models its own data.

    The cost appears when a second and third source arrive. Each API brings its own request rules, its own field names and its own failure behaviour, so your application ends up owning the field mapping, the product matching and the quality checks for every source.

    kwery moves that work below the API. Every supported marketplace returns the same fields, with the matched product, the offers, data-health flags and full source-and-timestamp details included, so adding a source adds coverage rather than another integration. The trade-off is a defined source library instead of an open portfolio.

    Architecture

    One API per source ←→ One API for all sources

    Traject Data

    One API per source, each with its own field names

    Amazon API
    Walmart API
    eBay API
    Your field-mapping layer

    kwery

    One API for every supported source

    Request per SKU + source
    Managed collection
    Matched product + data health + source details
    Your pricing logic

    Both paths deliver marketplace data. They differ in what your application receives and what it still has to model.

    If the underlying layers are still unclear, the marketplace data infrastructure guide describes what sits between a marketplace and a production record.

    If Amazon is the only source in scope, the portfolio question narrows to one product: Rainforest API and kwery, compared on Amazon covers Amazon-native request types and Amazon field coverage in detail.

    How Traject Data and kwery Compare

    Each row is either a shared capability, a genuine strength of the other product, or a kwery capability the other product does not document. Verify every row against current documentation during evaluation.

    Traject Data and kwery compared capability by capability
    • 01

      Relevant source coverage

      Traject Data

      Strong US retail portfolio, one API per source

      kwery

      European and global marketplace library behind one API

    • 02

      How much detail per source

      Traject Data

      High per source; Amazon depth is a particular strength

      kwery

      Direct collection with marketplace seller, shipping and availability preserved

    • 03

      Finding the right product

      Traject Data

      You supply the source's own identifier (ASIN, item ID) or a URL; barcodes are not supported

      kwery

      Barcode or marketplace ID resolved to the product on that marketplace, with a match confidence returned

    • 04

      Same fields across sources

      Traject Data

      Your application maps each source's field names

      kwery

      Every source returns the same fields

    • 05

      Can you trust the data?

      Traject Data

      Not offered, you get a response status, not a confidence signal

      kwery

      A trust score and data-health flags come back with every record

    • 06

      Where the data came from

      Traject Data

      Basic request details, in each API's own format

      kwery

      Every record says which source, which country, how it was collected and when

    • 07

      What changed since last time

      Traject Data

      You compare two responses yourself, per source

      kwery

      A structured change record when the next reading differs from the previous one

    • 08

      How the data reaches your system

      Traject Data

      Synchronous and batch requests per API

      kwery

      Synchronous single lookups (wait), batch jobs and webhooks across all sources

    • 09

      Pricing transparency

      Traject Data

      Per-product credit models; verify each API separately

      kwery

      One credit per complete SKU dataset: one SKU, one source, fetched fresh. Matching the product, the product data and the offers are all included.

    Verify each row against current documentation during evaluation. Last verified: September 2026.

    What Comes Back With Each Record

    Both products return prices and offers. The rows below show what else is attached to a record when it reaches your system, and which side provides it.

    What comes back with one record in Traject Data and in kwery, point by point.
    01

    Coverage

    Which marketplaces can I read?

    Both

    Traject Data

    Amazon, Walmart, Target and further US retail APIs

    kwery

    Amazon, Google Shopping, Idealo, eBay, Walmart, Otto, Kaufland and further supported sources

    02

    Collection

    Who runs the retrieval?

    Both

    Traject Data

    Managed retrieval, one API per source

    kwery

    Managed retrieval from the requested marketplace

    03

    Product matching

    Can I start from a barcode?

    kwery only

    Traject Data

    No GTIN matching offered; lookups run on the source's own identifier (ASIN, item ID) or URL, so the resolution layer stays with you

    kwery

    Give a barcode (GTIN/EAN), ASIN or marketplace ID and get the matching product on that marketplace, with a match confidence

    04

    Requests per product

    How many requests does one complete product take?

    kwery only

    Traject Data

    Three on Amazon (search, product, offers); two on the other source APIs

    kwery

    One credit per complete SKU dataset, per source; On Amazon, Walmart and eBay, one credit covers 2 complete SKU datasets (search + product + offers, matched, each).

    05

    Response format

    Does one integration read every source?

    kwery only

    Traject Data

    Each API has its own field names; your application maps them

    kwery

    The same response format for every source

    06

    Can you trust the data?

    Should my system act on this price?

    kwery only

    Traject Data

    Not offered, the response carries the data, not a confidence signal

    kwery

    A trust score and data-health flags come back with every record

    07

    Where the data came from

    Can I see where and when this was collected?

    kwery only

    Traject Data

    Not offered, no source, method or timestamp details documented

    kwery

    Every record says which source, which country, how it was collected and when

    08

    What changed since last time

    What changed since the last reading?

    kwery only

    Traject Data

    Compared downstream from stored responses

    kwery

    A structured change record when the next reading differs from the previous one

    09

    Application layer

    Where does the pricing logic live?

    Both

    Traject Data

    None, the pricing logic stays in your systems

    kwery

    None, the pricing logic stays in your systems

    10

    Source-native depth

    Can I read source-specific surfaces?

    Traject Data only

    Traject Data

    Distinct request types per surface, including reviews, search and category

    kwery

    A fixed set of fields; some source-specific surfaces are out of scope

    Design emphasis, not quality ranking

    How Price and Offer Changes Are Detected

    kwery discovers a change when the next reading differs from the previous one and sends a structured change record through the configured delivery workflow, a real difference between two readings, not a platform alert.

    Traject Data's request types return search results or product data for the moment of the request. There is no delta between two collections, so change detection is built and maintained downstream, per source API.

    Detected Change Event

    1. Observation T1€129,90
    2. Marketplace changesunknown
    3. Observation T2€119,90

    kwery detects

    €129,90 → €119,90

    kwery discovers a change when the next marketplace observation differs from the previous one. It does not know the exact instant the marketplace changed. The structured delta is then emitted through the configured delivery workflow.

    Compare Cost per Usable Dataset, Not Cost per Credit

    The comparable figure is what each side charges for one complete SKU dataset.

    How we compare cost per dataset

    Traject Data’s unit

    Variable

    2–3

    requests per complete SKU dataset, per source

    • Amazon3 requests, search, product, offers
    • Other sources2 requests, search and product
    • MatchingNot sold at any request count
    • PlansOne subscription per source API

    kwery’s unit

    Fixed

    1

    credit per complete SKU dataset, everything included

    • 1 creditper SKU × source × fresh fetch
    • Includedmatching, product data and offers
    • Cache hitsno additional credit
    • Rolloverunused paid credits while active

    On Amazon, Walmart and eBay, one kwery credit covers 2 complete SKU datasets (search + product + offers, matched, each). All other sources: one credit, one complete SKU dataset.

    Billing unit

    Traject Data
    Each source API carries its own plan and request unit. A complete product view takes a search request plus a product request, and on Amazon a third request for the offer list.
    kwery
    One credit per complete SKU dataset: one SKU, one source, fetched fresh. Matching the product, the product data and the offers are all included.

    When several source APIs are combined, compare the total cost of one complete SKU dataset rather than the individual request prices.

    kwery charges one unit for one complete SKU dataset: no separate matching step, no separate lookup, no per-endpoint stacking, so the cost of an integration can be calculated before it is built.

    What One Complete Dataset Costs

    The steps below are drawn from publicly available documentation and should be verified against current documentation during evaluation.

    01

    Find the product

    Traject Data

    1 request, search by keyword or source identifier; barcode matching is not offered

    kwery

    Included, barcode, ASIN or marketplace ID matched in the same call

    02

    Product data

    Traject Data

    1 request, the source's product endpoint

    kwery

    Included in the same call

    03

    Offers

    Traject Data

    1 request on Amazon; other source APIs return the listing offer with the product

    kwery

    Included in the same call

    04

    Matching the product on that marketplace

    Traject Data

    Built and maintained in your systems

    kwery

    Included, matched within the requested source

    One complete SKU dataset

    Traject Data

    2–3 requests per source

    kwery

    1 credit

    Requests per complete product, by source API

    01

    Amazon

    API
    Rainforest API
    Requests
    3
    What they cover
    Search, product, offers
    02

    Walmart

    API
    BlueCart API
    Requests
    2
    What they cover
    Search and product; no separate offers endpoint
    03

    eBay

    API
    Countdown API
    Requests
    2
    What they cover
    Search and product; the listing is the offer
    04

    Home Depot

    API
    BigBox API
    Requests
    2
    What they cover
    Search and product; no offers endpoint
    05

    Lowe's

    API
    Backyard API
    Requests
    2
    What they cover
    Search and product; no offers endpoint
    06

    Target

    API
    RedCircle API
    Requests
    2
    What they cover
    Search and product; no offers endpoint
    07

    Google Shopping

    API
    Value / Scale SERP
    Requests
    2
    What they cover
    Shopping search and product details

    None of Traject Data's source APIs offers GTIN matching: they return search results, product records and, on Amazon, offers. Turning a barcode into the right product on each marketplace remains work the customer builds and maintains. Request counts should be verified against each API's current documentation.

    When Traject Data or kwery Is the Better Fit

    Neither option is the general answer. The requirement decides, and the requirement is usually clearer than the feature comparison.

    Traject Data may fit better when

    • one US marketplace dominates the requirement
    • you need source-native request types and fields with nothing abstracted
    • Amazon-specific surfaces such as reviews, search or category data are in scope
    • products are already identified by ASIN, item ID or URL
    • your team already owns a field-mapping layer it is happy to maintain

    kwery may fit better when

    • a GTIN or EAN is the input and matching should not be built in-house
    • three or more marketplaces feed the same downstream system
    • European sources such as Idealo, Otto or Kaufland are part of the requirement
    • you want matching, data-health checks and source details handled before delivery
    • you would rather not maintain per-source failure and quality handling

    Before You Switch

    A provider migration is not only an API-key change. These considerations are specific to moving between Traject Data and kwery:

    Retire Your Field-Mapping Layer

    Code that reconciles Amazon, Walmart and eBay shapes can usually be removed. Inventory it first, it often holds business rules worth keeping.

    Request Type Mapping

    Source-specific request types become one request per SKU and source. Confirm which surfaces you genuinely consume before assuming parity.

    Source Parity Check

    Verify that every marketplace and country you use today exists in the kwery source library before planning the move.

    General migration checklist

    Identifier Compatibility
    Can existing GTINs, EANs, UPCs, ASINs or source URLs be reused as request inputs?
    Schema Migration
    Which fields change name, type or meaning, and which consumers read them today?
    Source Parity
    Are all required marketplaces and countries available on both sides of the move?
    Freshness Semantics
    Does "fresh" mean the same thing in both systems, and does every record carry a collection timestamp?
    Offer Modeling
    Are seller, shipping and availability represented in equivalent ways?
    History
    Will historical records need to remain in the existing system, and for how long?
    Failure Handling
    How should the application interpret unresolved products and partial results?
    Billing Unit
    Are you paying by request, credit, record, product/source lookup or another unit?

    Product capabilities and pricing can change. This comparison is based on publicly available product and documentation information and should be verified against current documentation during evaluation. Traject Data and other third-party names are trademarks of their respective owners. kwery is not affiliated with, endorsed by, or sponsored by Traject Data.

    Support

    Traject Data Comparison Questions

    Short answers to the questions teams ask when evaluating Traject Data and kwery side by side.

    Browse all FAQs

    Rainforest API is the Amazon product inside the Traject Data portfolio, so an Amazon-only comparison is a subset of this one. If Amazon is the only source in scope, weigh source-native depth heavily and read the dedicated Rainforest API comparison; if other marketplaces are in scope, the question of one shared format dominates. Read the Rainforest API comparison.

    Shared fields mean equivalent concepts have the same names and types, not that marketplace detail disappears. Check the specific Amazon fields your logic reads against the kwery record before deciding.

    Yes. Some teams keep a source-native API for one deep Amazon workflow and use kwery for the multi-marketplace pricing path.

    Each API adds its own request rules, field names, identifiers and failure behaviour, so your application owns the field mapping, the product matching and the quality checks for every source. kwery moves that work below the API; the trade-off is a defined source library instead of an open portfolio.

    Compare With Real SKUs, Not Feature Pages

    The most useful evaluation uses your marketplaces, your identifiers, your edge cases and your downstream schema.

    Get API KeyView Documentation
    Free Tier Available
    Enterprise SLA
    Global Scale