/misumi/products/variants

POST /api/misumi/products/variants

Price: 20 credits

List the part numbers (型番) of a MISUMI (ミスミ) series: part number, unit price in JPY excluding tax, pieces per package, minimum order quantity, shipping lead time, stock flag, RoHS status, CAD availability, the full specification values that distinguish the item, and attached documents. Can be narrowed to a configuration and ordered by price or lead time.

How to use it

List every part number (型番) inside one MISUMI series — the concrete orderable items of a configurable family, each with its own price and lead time. Accepts a series code, any part number of that series, or a product URL. `specs` on each row are the values that make this item different from its siblings (thread size, length, material, finish …): `value` is what the storefront prints and `filter_value` is what `attributes` takes to narrow the list to one configuration. Prices are JPY excluding consumption tax; `pieces_per_package` tells whether the price is per piece or per box.

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", "https://jp.misumi-ec.com/vona2/detail/110302280360/"; minLength: 1)
• count integer required — Max number of part numbers to return (min: 1)
• attributes object nullable — Narrow the part numbers to a configuration, as {specification id: value}. Take the id from `specs[].id` of a part number and the value from its `filter_value`, or from the `filters` of a category in misumi/categories (examples: {"SP100255878":"20220906084836058512376"})
  • * string
• sort string — Result ordering (default: "catalog"; one of: "catalog", "days_to_ship_asc", "days_to_ship_desc", "price_asc", "price_desc")

Response

• @type string (default: "MisumiVariant")
• id string required
• url string required
• series_id string required
• part_number string required
• inner_code string nullable
• inner_name string nullable
• inner_name_en string nullable
• type_code string nullable
• price number nullable
• currency string (default: "JPY")
• pieces_per_package integer nullable
• min_quantity integer nullable
• order_unit integer nullable
• min_days_to_ship integer nullable
• max_days_to_ship integer nullable
• min_shortest_days_to_ship integer nullable
• max_shortest_days_to_ship integer nullable
• is_stock_item boolean nullable
• is_discontinued boolean nullable
• is_sales_stopped boolean nullable
• sales_stop_message string nullable
• is_special_shipment boolean nullable
• is_prompt_delivery boolean nullable
• has_volume_discount boolean nullable
• part_number_pattern string nullable
• cad_types array (default: [])
• labels array (default: [])
• notes array (default: [])
• cautions array (default: [])
• specs array (default: [])
  • @type string (default: "MisumiSpec")
  • id string required
  • name string required
  • value string required
  • filter_value string nullable
  • group string nullable
  • group_value string nullable
  • code string nullable
  • unit string nullable
  • image string nullable
  • diagram string nullable
• documents array (default: [])
  • @type string (default: "MisumiDocument")
  • name string required
  • url string required

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.