/hepsiburada/products/sellers

POST /api/hepsiburada/products/sellers

Price: 20 credits

List all sellers (merchants) offering a Hepsiburada product by SKU, product group id or product URL: seller id, name, price, list_price, rating, city, shipping flags and which seller wins the buybox.

How to use it

List every seller (merchant) that offers a given Hepsiburada product, by SKU (HBCV...), product group id (HBC...) or product URL. Each offer has seller_id, seller_name, seller_alias, listing_id, price, list_price, currency (TRY), rating, rating_count, city, has_free_shipping, has_fast_shipping and is_winner (the seller that wins the buybox). Use it to compare prices across sellers.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — Hepsiburada product SKU, product group id or a product URL (examples: "HBCV00004X9ZCH", "HBC00004X9ZCG", "https://www.hepsiburada.com/apple-iphone-15-128-gb-p-HBCV00004X9ZCH"; minLength: 1)

Response

• @type string (default: "HepsiburadaProductOffer")
• seller_id string required
• seller_name string nullable
• seller_alias string nullable
• listing_id string nullable
• price number nullable
• list_price number nullable
• currency string nullable
• rating number nullable
• rating_count integer nullable
• city string nullable
• has_free_shipping boolean nullable
• has_fast_shipping boolean nullable
• is_winner boolean 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/product id, or page has no sellers) 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.