/cdiscount/products/offers

POST /api/cdiscount/products/offers

Price: 1 credit

Get all seller offers for a Cdiscount product (product URL or sku): each offer's price and tax-excluded price, condition, seller name and rating, seller sales count, shipping country and free-shipping label.

How to use it

List the competing seller offers for a single Cdiscount product (pass the product URL or sku). Each offer has id (offer id), price/price_without_vat/currency, condition (New/Used/Refurbished), seller_name/seller_id/seller_rating/seller_review_count/seller_sales_count/seller_country and url.

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 URL (preferred, carries the category id) or product id (sku) (examples: "https://www.cdiscount.com/telephonie/telephone-mobile/x/f-14404-ip17prom256orang.html", "ip17prom256orang"; minLength: 1)

Response

• @type string (default: "CdiscountOffer")
• id string required
• product_id string nullable
• price number nullable
• price_without_vat number nullable
• currency string (default: "EUR")
• condition string nullable
• is_cdav boolean nullable
• free_shipping_label string nullable
• seller_name string nullable
• seller_id string nullable
• seller_rating number nullable
• seller_review_count integer nullable
• seller_sales_count integer nullable
• seller_country string nullable
• seller_comments string nullable
• url string 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 or has no available offers 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.