/cdiscount/products

POST /api/cdiscount/products

Price: 5 credits

Get full Cdiscount product details by product id (sku) or product URL: title, brand, EAN, price and tax breakdown, condition, availability, images, description, technical specifications, variants, seller, offer counts and price range across sellers, energy grade and related searches.

How to use it

Fetch a single Cdiscount product by sku or product URL. Returns one item with title, brand, ean, image/images, description, price/price_without_vat/currency/taxes, condition (New/Used/Refurbished), is_available, seller_name/seller_id/seller_sales_count, offer_count/new_offer_count/used_offer_count, lowest_new_price/lowest_used_price (across all sellers), bullet_points, specifications (group/name/value), variants and related_searches.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — Cdiscount product id (sku) or a product URL containing it (examples: "ip17prom256orang", "https://www.cdiscount.com/telephonie/telephone-mobile/x/f-14404-ip17prom256orang.html"; minLength: 1)

Response

• @type string (default: "CdiscountProduct")
• id string required
• offer_id string nullable
• url string nullable
• brand string nullable
• brand_id string nullable
• ean string nullable
• manufacturer_model string nullable
• image string nullable
• images array (default: [])
• image_count integer nullable
• description string nullable
• short_description string nullable
• price number nullable
• price_without_vat number nullable
• currency string (default: "EUR")
• taxes array (default: [])
  • @type string (default: "CdiscountProductTax")
  • type string required
  • value number nullable
• condition string nullable
• is_available boolean nullable
• is_free_shipping boolean nullable
• free_shipping_label string nullable
• seller_name string nullable
• seller_id string nullable
• seller_sales_count integer nullable
• category_id string nullable
• category_path string nullable
• department_id string nullable
• offer_count integer nullable
• new_offer_count integer nullable
• used_offer_count integer nullable
• lowest_new_price number nullable
• lowest_used_price number nullable
• energy_grade string nullable
• repairability_index number nullable
• is_trade_in_eligible boolean nullable
• related_searches array (default: [])
• bullet_points array (default: [])
• specifications array (default: [])
  • @type string (default: "CdiscountProductSpec")
  • group string required
  • name string required
  • value string required
• variants array (default: [])
  • @type string (default: "CdiscountProductVariant")
  • key string required
  • sku string required
  • url string nullable
  • price number nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Product not found (well-formed but nonexistent sku) Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.