/madeinchina/companies

POST /api/madeinchina/companies

Price: 10 credits

Get a Made-in-China supplier/manufacturer profile by subdomain slug or supplier URL: name, business type, establishment date, employees, address, registered capital, main markets, incoterms, terms of payment, lead time, export experience, nearest port, main products and audited status.

How to use it

Fetch a single Made-in-China supplier by subdomain slug (e.g. 'cx-led') or supplier URL. Returns one item with id, name, url, is_audited, is_diamond, business_type, established_date, employee_count, address, registered_capital, plant_area, main_markets, incoterms, terms_of_payment, average_lead_time, export_experience, nearest_port, min_order, main_products and the full info map.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• company string required — Made-in-China supplier subdomain slug or a supplier URL (examples: "cx-led", "https://cx-led.en.made-in-china.com/"; minLength: 1)

Response

• @type string (default: "MadeinchinaCompany")
• id string required
• name string nullable
• url string nullable
• about_url string nullable
• is_audited boolean (default: false)
• is_diamond boolean (default: false)
• business_type string nullable
• established_date string nullable
• employee_count integer nullable
• address string nullable
• registered_capital string nullable
• plant_area string nullable
• main_markets string nullable
• incoterms string nullable
• terms_of_payment string nullable
• average_lead_time string nullable
• export_experience string nullable
• nearest_port string nullable
• min_order string nullable
• main_products array (default: [])
• info object (default: {})
  • * string

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 — Supplier not found (well-formed slug/URL but the supplier does not exist) 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.