/tradeindia/companies/products

POST /api/tradeindia/companies/products

Price: 45 credits

List the products of a TradeIndia seller company, all categories or one: name, price, minimum order, unit, category and image

How to use it

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

timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
company string required — TradeIndia company URL or company id (examples: "https://www.tradeindia.com/zaral-electricals-6707422/", "6707422"; minLength: 1)
category string nullable — Product category of this company, from tradeindia/companies (examples: "https://www.tradeindia.com/zaral-electricals-6707422/electric-boxes.html", "electric-boxes"; minLength: 1)
count integer required — Max number of results (min: 1; max: 1000)

@type string (default: "TradeindiaProductLink")
id string required
url string required
name string nullable
description string nullable
listing_type string nullable
price string nullable
price_details array (default: [])
- @type string (default: "TradeindiaField")
- label string required
- value string required
min_order_quantity integer nullable
unit string nullable
image string nullable
category_id integer nullable
category string nullable
category_url string nullable
created_date integer nullable
company_id integer nullable
company_name string nullable
company_url string nullable
city string nullable
state string nullable

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 — TradeIndia has no company under that id, 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.

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.