Otto API · Marketplace Price & Offer Data

OTTO retail and third-party marketplace pricing, seller, and availability data across Germany, built for repricing on DE's second-largest marketplace

Get API Key API ReferenceView API Reference

· Free tier available · Plans from €79/mo

Coverage

Germany

Delivery

Webhooks or Polling

Integration

One API Endpoint

Schema

Complete Otto Marketplace Data

One unified schema covering Otto's retail catalog and third-party marketplace. Pricing, sellers, and availability in one structure.

View Full Schema

content

13 fields

Sourcesource

Product Namename

Brandbrand_name

GTINgtin

Product IDproduct_id

URLurl

Image URLimage_url

Currencycurrency

…

offers[]

12 fields

Positionposition

Seller Nameseller_name

Marketplacemarketplace_name

Seller Typeseller_type

Seller Ratingseller_rating

Seller Rating Countseller_rating_count

Priceprice

Shippingshipping

…

otto fields

16 fields

Variation IDvariation_id

Article Numberarticle_number

Sponsoredsponsored

On Saleon_sale

Starting Priceis_starting_price

Availability Textavailability_text

Categorycategory

Idid

…

Developer Experience

One Endpoint.
Multiple Sources

Otto is a native integration within the kwery API. No separate implementation required.

Otto data is available through the same kwery API endpoint as all other sources. Specify source: "otto" in your request. Same webhook delivery, same audit trails, same reliability guarantees.

Stream results as they complete. Use the same pipeline you already use for Amazon DE and Idealo DE.

View API Reference

POST · api.kwery.co/stream

200 OK

# Submit a job querying Otto Germany
curl -X POST "https://api.kwery.co/stream" \
  -H "Authorization: Bearer $KWERY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "source": "otto",
    "country": "de",
    "key": "term",
    "values": ["Bosch Serie 6"],
    "callback_url": "https://your-app.example.com/webhook"
  }'

Data Quality

Know What Your Pricing Logic Is Acting On

Quality and provenance signals help you assess product matching, result confidence, and request history before data enters production workflows.

Trust Score

A compact quality signal helps your pipeline assess product identity, completeness, price integrity, and freshness together.

Check quality before pricing logic.

{
  "source" otto,
  "trust" {
    "score" 0.92,
    "detail" {
      "identity" 1.00,
      "completeness" 0.89,
      "price_integrity" 0.95,
      "freshness" 0.75
    }
  }
}

Match Confidence

See how confidently the request was resolved to the intended Otto product before using its offers downstream.

Surface ambiguous matches for review.

{
  "source" otto,
  "key" gtin,
  "value" 4006381333962,
  "match" {
    "product_id" 123456789,
    "confidence" 1.00,
    "ambiguous" false
  }
}

Audit Trail

Job identifiers and observation timestamps let your team connect a delivered result to the request that produced it.

Keep data-driven decisions traceable.

{
  "job_id" 01J3R5T7Z9,
  "source" otto,
  "country" de,
  "observed_at" 2026-09-24T09: 12: 04Z,
  "status" completed,
  "result_count" 1
}

Germany

Complete Otto Coverage for the German Market

Otto.de is a German-focused marketplace. kwery covers the full Otto.de catalog including marketplace seller offers.

1 Market

deGermany

Self-Serve

One Credit. One Resolved SKU

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

Product Matching

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

Product Page

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

Offers

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

Entry Price

€79 / mo

Included

10k credits / mo

Included Usage

10k Otto SKUs / mo

Get API Key View Pricing

Free tier available · 1,000 one-time credits, no credit card required.

Enterprise

Need Custom Pricing, SLAs, or Support?

Dedicated volume pricing, custom SLAs, and direct engineering support for teams running millions of SKUs.

Talk to Sales

Use Cases

What Teams Build With
Otto Data

One endpoint feeds the systems engineering teams ship to production, repricing, monitoring, sourcing, and intelligence.

Buybox Repricing

React to Buybox losses by streaming winner changes per EAN into your repricing engine. Otto's own documentation confirms the factors: price, shipping cost, delivery time, and seller trust, not price alone.

See how Otto repricing works

Seller Intelligence

Track competing offers, delivery promises, and seller trust signals to model competitive pressure per product.

See Otto seller intelligence

MAP & Brand Protection

Monitor seller identity, observed offer price, shipping, delivery, and trust context across Otto Market.

See how MAP monitoring works

Building an AI Shopping Agent?

Support

Common Questions

Answers to Otto-specific questions about marketplace data and integration.

Browse all FAQs

Yes. Both Otto's first-party retail offers and third-party marketplace seller offers are returned, with a clear seller-type flag on each.

Both the current price and the original/list price are returned. Promotional flags are surfaced so your engine can react to Otto-driven discount cycles instead of treating sale prices as the new baseline.

Both. kwery resolves EANs to Otto product pages automatically; if you already have Otto SKUs, you can pass them directly.

Yes. Delivery cost and estimated delivery days are exposed per offer, both matter for German conversion modeling.

Live on every request. Streaming jobs deliver results as soon as collection completes.

Otto exposes first-party retail offers alongside third-party marketplace sellers, with German-market delivery cost and delivery time on every offer, signals that matter for DACH conversion modeling and don't surface cleanly on Amazon or Idealo. Promotional flags distinguish Otto-driven discount cycles from baseline pricing.

More Marketplaces