/indiamart/companies/products

POST /api/indiamart/companies/products

Price: 20 credits

List the products of an IndiaMART supplier, all categories or one: name, price, unit, minimum order, specifications, description, images and category

How to use it

Category URLs come from product_categories of indiamart/companies. Pass a returned url to indiamart/products for the full product page with seller details.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company string required — IndiaMART company alias or mini-site URL (examples: "ledlightingworld", "https://www.indiamart.com/ledlightingworld/"; minLength: 1)
• category string nullable — Product category of this company, from indiamart/companies (examples: "https://www.indiamart.com/ledlightingworld/led-photo-frame.html", "led-photo-frame"; minLength: 1)
• count integer required — Max number of results (min: 1; max: 1000)

Response

• @type string (default: "IndiamartCatalogProduct")
• id string required
• url string nullable
• name string nullable
• price string nullable
• price_value number nullable
• unit string nullable
• min_order_quantity integer nullable
• min_order_unit string nullable
• description string nullable
• specifications array (default: [])
  • @type string (default: "IndiamartSpec")
  • label string required
  • value string required
• additional_information array (default: [])
• brochure_url string nullable
• image string nullable
• images array (default: [])
• video string nullable
• category_id string nullable
• category string nullable
• category_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 — IndiaMART has no company under that alias, or the company has no product category under that name 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.