/monotaro/products

POST /api/monotaro/products

Price: 20 credits

Get a MonotaRO (モノタロウ) product by order code (注文コード), product-group code or product URL: name, brand, maker product code, prices with and without tax, list price, shipping lead time, rating, review count, category breadcrumbs, images, the full specification table and linked documents (safety data sheets, RoHS certificates, product Q&A).

How to use it

Fetch one MonotaRO (モノタロウ, Japanese B2B industrial/MRO catalog) product. Accepts an order code (注文コード, 8 digits, keep leading zeros, e.g. '02197517'), a product-group code (商品コード, e.g. '00005036') or a full /p/ or /g/ product URL. An order code identifies a single SKU (one exact size / variant); a product-group code identifies the whole family and returns family-level fields plus the cheapest and most expensive variant price. The two code spaces overlap: the same eight digits are often valid in both and then name two different products, so set `code_type` to say which one you have (or pass the URL, which is self-describing). The answer always names both `order_code` and `product_code`, so you can tell what you got. Prices are JPY: `price`/`price_with_tax` are the selling price without and with consumption tax, `list_price` is the manufacturer reference price. `min_ship_days`/`max_ship_days` are the lead time in days (0 = ships the same day); for a single SKU both are the same number, for a family they span its SKUs. `documents` links the PDFs attached to the product — safety data sheet (SDS), RoHS compliance certificate, product Q&A. `variant_count` tells how many SKUs the family has — use monotaro/products/variants to list them.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — MonotaRO order code (注文コード, e.g. '02197517'), product-group code (商品コード, e.g. '00005036'), or a full product URL (examples: "02197517", "https://www.monotaro.com/p/0219/7517/", "https://www.monotaro.com/g/00005036/"; minLength: 1)
• code_type string — Which code space `product` belongs to when it is passed as bare digits. The two code spaces overlap — the same eight digits can name one SKU and a different whole product family. Ignored when `product` is a URL (default: "order_code"; one of: "order_code", "product_code")

Response

• @type string (default: "MonotaroProduct")
• id string required
• url string required
• order_code string nullable
• product_code string required
• product_url string required
• name string required
• sub_name string nullable
• brand string nullable
• brand_id string nullable
• maker_product_code string nullable
• image string nullable
• images array (default: [])
• description string nullable
• attention string nullable
• usage string nullable
• price number nullable
• price_with_tax number nullable
• list_price number nullable
• list_price_with_tax number nullable
• min_price number nullable
• max_price number nullable
• currency string (default: "JPY")
• quantity string nullable
• min_ship_days integer nullable
• max_ship_days integer nullable
• is_orderable boolean nullable
• is_private_brand boolean nullable
• can_subscribe boolean nullable
• is_sellable_to_consumer boolean nullable
• rating number nullable
• review_count integer nullable
• variant_count integer nullable
• category string nullable
• category_id string nullable
• breadcrumbs array (default: [])
  • @type string (default: "MonotaroCategoryRef")
  • id string required
  • name string required
  • url string required
• specs object (default: {})
  • * string
• documents array (default: [])
  • @type string (default: "MonotaroDocument")
  • 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 — Product not found (well-formed code but no such product on MonotaRO) 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.