/misumi/products/similar

POST /api/misumi/products/similar

Price: 1 credit

List the MISUMI (ミスミ) series the source itself presents as alternatives to a given series (類似品): id, name, marketing description, manufacturer and images.

How to use it

Alternatives to one MISUMI series, as published by the source itself. Accepts a series code, a part number (型番) of the series, or a product URL. Feed a returned `id` into misumi/products for the full record. The list is short and curated by MISUMI — it is not a search; use misumi/products/search to look for products by specification. A series with no published alternatives returns an empty list.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — MISUMI series code (e.g. '110302280360'), a part number (型番) belonging to the series, or a full product URL (examples: "110302280360", "BOX-CBE3-10"; minLength: 1)
• count integer required — Max number of similar series to return (min: 1)

Response

• @type string (default: "MisumiSimilarProduct")
• id string required
• url string required
• name string required
• description string nullable
• brand object nullable
  • @type string (default: "MisumiBrandRef")
  • id string required
  • name string required
  • alias string nullable
  • url string nullable
  • is_misumi boolean nullable
• image string nullable
• images array (default: [])
  • @type string (default: "MisumiImage")
  • url string required
  • caption 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 — Series not found (well-formed series code or part number, but no such product 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.