/flipkart/products

POST /api/flipkart/products

Price: 10 credits

Get full Flipkart product details by item id (or product URL): title, brand, price, list_price, discount, images, color, rating, ratings and reviews count, category, breadcrumbs, availability, condition and recent customer reviews.

How to use it

Fetch a single Flipkart product by item id (itm...) or a product URL. Returns one item with title, brand, description, price/list_price/discount_percentage/currency (INR), image+images, color, rating, rating_count, review_count, category+breadcrumbs, availability/is_in_stock, condition (new/used) and reviews (recent customer reviews with title/author/rating/text/date).

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 containing it (examples: "itm6ac6485515ae4", "https://www.flipkart.com/apple-iphone-15-black-128-gb/p/itm6ac6485515ae4?pid=MOBGTAGPTB3VS24W"; minLength: 1)

Response

• @type string (default: "FlipkartProduct")
• id string required
• product_id string nullable
• url string required
• alias string nullable
• brand string nullable
• description string nullable
• price number nullable
• list_price number nullable
• discount_percentage number nullable
• currency string nullable
• image string nullable
• images array (default: [])
• color string nullable
• rating number nullable
• rating_count integer nullable
• review_count integer nullable
• category string nullable
• breadcrumbs array (default: [])
• availability string nullable
• is_in_stock boolean nullable
• condition string nullable
• reviews array (default: [])
  • @type string (default: "FlipkartProductEmbeddedReview")
  • author string nullable
  • rating number nullable
  • text string nullable
  • date 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 (well-formed but nonexistent item id, or page has no product) 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.