/misumi/manufacturers/search

POST /api/misumi/manufacturers/search

Price: 20 credits

List or search the manufacturers (メーカー) carried by MISUMI (ミスミ): id, name, English name, URL slug, storefront URL, search synonyms and whether the brand is MISUMI's own.

How to use it

The manufacturer index of MISUMI — MISUMI's own label plus the third-party brands it distributes. `keyword` matches the name, the id and the brand's registered synonyms, so both 'SMC' and a Japanese trade name resolve. Omitting `keyword` returns the whole index, which is large, so prefer a keyword when you can. Feed an `id` into misumi/manufacturers for the manufacturer's categories, or into misumi/products/search as `brand` to list its products.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string nullable — Match against manufacturer name, id and search synonyms. Omit to list every manufacturer (examples: "SMC", "ミスミ"; minLength: 1)
• count integer required — Max number of manufacturers to return (min: 1)

Response

• @type string (default: "MisumiBrand")
• id string required
• name string required
• alias string nullable
• url string nullable
• is_misumi boolean nullable
• name_en string nullable
• website_url string nullable
• image string nullable
• description string nullable
• index_character string nullable
• synonyms array (default: [])

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.