/flipkart/sellers

POST /api/flipkart/sellers

Price: 10 credits

Get the Flipkart seller (store) offering a given product, by item id or product URL: seller name, seller rating, years on Flipkart, units sold, quality and speed scores, product-quality and service-quality ratings, and the seller description.

How to use it

Fetch the marketplace seller behind a Flipkart product, identified by item id (itm...) or a product URL. Returns one seller with id, name, rating, years_with_flipkart, product_sold (units, e.g. '1.1L+'), quality_score and speed_score (percent), product_quality_rating and service_quality_rating (out of 5), description, and product_id (the product this seller offers). Flipkart exposes seller data only in the context of a product, so the input is a product, not a bare seller id.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — Flipkart product item id or a product URL — returns the seller (store) offering that product (examples: "itm6ac6485515ae4", "https://www.flipkart.com/apple-iphone-15-black-128-gb/p/itm6ac6485515ae4?pid=MOBGTAGPTB3VS24W"; minLength: 1)

Response

• @type string (default: "FlipkartSeller")
• id string nullable
• name string nullable
• rating number nullable
• years_with_flipkart integer nullable
• product_sold string nullable
• quality_score number nullable
• speed_score number nullable
• product_quality_rating number nullable
• service_quality_rating number nullable
• description string nullable
• product_id 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 — Seller not found (nonexistent product, or the product page carries no seller block) 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.