/madeinchina/products/search

POST /api/madeinchina/products/search

Price: 20 credits

Search Made-in-China products by keyword. Returns B2B offer cards: title, FOB price range, MOQ, specification attributes, images, audited badges and the supplier. Filter by category, province, price range, minimum order, business type and audited status.

How to use it

Search the Made-in-China B2B catalog by keyword. Each item has id, product_title, product_url, price/price_max (FOB), moq/moq_unit, attributes (spec key/values), is_audited, is_leading_factory, image and supplier (name, alias, url). Optional filters: category, province, min_price/max_price, min_order, business_type, audited_supplier, leading_factory.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string required — Search keyword (examples: "led light", "phone case"; minLength: 1)
• count integer required — Max number of products to return (min: 1)
• category string nullable — Filter by product category (one of: "agriculture-food", "apparel-accessories", "arts-crafts", "auto-motorcycle-parts", "bags-cases-boxes", "chemicals", "computer-products", "construction-decoration", "consumer-electronics", "electrical-electronics", "furniture", "health-medicine", "industrial-equipment", "instruments-meters", "light-industry-daily-use", "lights-lighting", "machinery", "metallurgy-mineral-energy", "office-supplies", "packaging-printing", "security-protection", "service", "sporting-goods", "textile", "tools-hardware", "toys", "transportation")
• province string nullable — Filter by supplier province in China (one of: "Guangdong", "Zhejiang", "Shandong", "Jiangsu", "Fujian", "Shanghai", "Hebei", "Anhui", "Henan", "Hubei", "Hunan", "Beijing", "Sichuan", "Tianjin", "Chongqing", "Jiangxi", "Shaanxi", "Liaoning", "Guangxi", "Yunnan", "Hainan", "Shanxi", "Hongkong", "Guizhou", "Jilin", "Heilongjiang", "Xinjiang", "InnerMongolia", "Gansu", "Taiwan")
• min_price number nullable — Minimum FOB unit price in USD (min: 0)
• max_price number nullable — Maximum FOB unit price in USD (min: 0)
• min_order integer nullable — Return offers whose minimum order quantity is at most this (min: 1)
• business_type string nullable — Filter by supplier business type (one of: "manufacturer", "trading-company", "group-corporation", "other")
• audited_supplier boolean — Only offers from audited suppliers (default: false)
• leading_factory boolean — Only offers from industry-leading audited factories (default: false)

Response

• @type string (default: "MadeinchinaProductCard")
• id string required
• product_title string nullable
• product_url string nullable
• price number nullable
• price_max number nullable
• price_text string nullable
• moq integer nullable
• moq_unit string nullable
• attributes object (default: {})
  • * string
• is_audited boolean (default: false)
• is_leading_factory boolean (default: false)
• image string nullable
• supplier object nullable
  • @type string (default: "MadeinchinaProductCardSupplier")
  • name string nullable
  • alias string nullable
  • 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 — 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.