/tradeindia/products/search

POST /api/tradeindia/products/search

Price: 20 credits

Search TradeIndia products by keyword, optionally in one city: product name, price, minimum order, specifications, category, seller company with location, business type, website and membership flags

How to use it

Pass a returned url to tradeindia/products for the full product page, or company_url to tradeindia/companies for the seller profile.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string required — Product keyword (examples: "led lights"; minLength: 1)
• city string nullable — City name (examples: "Mumbai"; minLength: 1)
• count integer required — Max number of results (min: 1; max: 5000)

Response

• @type string (default: "TradeindiaProductCard")
• id string required
• url string required
• name string nullable
• description string nullable
• short_description string nullable
• listing_type string nullable
• is_service boolean nullable
• price string nullable
• price_value number nullable
• price_min number nullable
• price_max number nullable
• price_range string nullable
• currency string nullable
• min_order_quantity integer nullable
• unit string nullable
• in_stock boolean nullable
• brand string nullable
• category_id integer nullable
• category string nullable
• product_category_id integer nullable
• product_category string nullable
• keywords array (default: [])
• image string nullable
• video string nullable
• specifications array (default: [])
  • @type string (default: "TradeindiaSpec")
  • group string nullable
  • label string required
  • value string required
• details_html string nullable
• created_date integer nullable
• company_id integer nullable
• company_name string nullable
• company_url string nullable
• company_website string nullable
• contact_designation string nullable
• business_types array (default: [])
• is_manufacturer boolean nullable
• is_supplier boolean nullable
• is_exporter boolean nullable
• is_trader boolean nullable
• is_distributor boolean nullable
• is_paid_member boolean nullable
• has_trust_stamp boolean nullable
• is_premium_seller boolean nullable
• is_super_seller boolean nullable
• is_made_in_india boolean nullable
• certification string nullable
• established_year integer nullable
• member_since_year integer nullable
• verified_date integer nullable
• last_active_date integer nullable
• address string nullable
• locality string nullable
• postal_code string nullable
• city string nullable
• city_id integer nullable
• state string nullable
• country string nullable
• country_code string nullable
• latitude number nullable
• longitude number 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 — The entity was not found, or a precondition failed 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.