/misumi/manufacturers

POST /api/misumi/manufacturers

Price: 20 credits

Get a MISUMI (ミスミ) manufacturer by id, URL slug or manufacturer URL: name, English name, search synonyms, storefront URL, how many series it sells on MISUMI, and the catalog categories it sells in.

How to use it

One manufacturer (メーカー) carried by MISUMI — MISUMI's own private label as well as the ~3200 third-party brands it distributes. Pass the manufacturer id as returned by our other endpoints (`brand.id`, e.g. 'SMC1'), or the URL slug the storefront uses ('smc'). The id is the cheap path: resolving a slug requires reading the whole manufacturer index. `series_count` is how many series the manufacturer has on MISUMI — list them with misumi/products/search and `brand` set to this id. `categories` are the catalog categories the manufacturer appears in.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• manufacturer string required — MISUMI manufacturer id (e.g. 'SMC1'), the manufacturer's URL slug (e.g. 'smc') or a full manufacturer URL (examples: "SMC1", "smc", "https://jp.misumi-ec.com/vona2/maker/smc/"; minLength: 1)

Response

• @type string (default: "MisumiManufacturer")
• 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: [])
• series_count integer nullable
• categories array (default: [])
  • @type string (default: "MisumiCategoryChild")
  • id string required
  • name string required
  • url string nullable
  • series_count integer 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 — Manufacturer not found (well-formed id or slug, but no such manufacturer on MISUMI) 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.