POST /api/monotaro/products/search
Price: 20 credits
Search the MonotaRO (モノタロウ) catalog by keyword, category, brand, part number, price range, rating, shipping lead time and category-specific attribute filters. Returns product cards with prices with and without tax, rating, review count, variant count, shipping lead time, category breadcrumbs, the representative specification set and linked documents.
Search MonotaRO (モノタロウ, Japanese B2B industrial/MRO catalog, ~29M SKUs). Every filter is optional except `count`; with no filters it browses the whole catalog. Results are product FAMILIES — `id` is a product-group code, `variant_count` says how many individual SKUs it holds, and `price` is the cheapest SKU (JPY, excluding tax) with `has_price_range` telling whether SKUs differ in price. `attributes` filters on category-specific properties (tip shape, thread size, glove material…): call monotaro/categories with that `category` id and copy an id and one of its values from the `filters` it returns. Use monotaro/products/variants to expand a family into individual order codes.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)keyword string nullable — Free-text search keyword (examples: "ドライバー", "六角ボルト")count integer required — Max number of results to return (min: 1)category string nullable — Category id to search within, as returned by monotaro/categories (examples: "27086")brand string nullable — Brand / manufacturer name (examples: "ベッセル", "TRUSCO")product_name string nullable — Match against the product name onlyorder_code string nullable — MonotaRO order code (注文コード) (examples: "02197517")maker_product_code string nullable — Manufacturer part number (品番) (examples: "220 +1X75")attributes object nullable — Category-specific attribute filters as {attribute id: value}. Ids and their allowed values differ per category and are listed in the `filters` of that category in monotaro/categories (examples: {"972":"プラス(+)"})* stringprice_min integer nullable — Minimum price in JPY, excluding tax (min: 0)price_max integer nullable — Maximum price in JPY, excluding tax (min: 0)min_rating integer nullable — Only products rated at least this many stars (min: 1; max: 4)max_ship_days string nullable — Only products that ship within this lead time (one of: "same_day", "next_day", "two_days", "three_days", "four_days")include_discontinued boolean — Include products that are no longer stocked (default: false)exclude_business_only boolean — Exclude products that cannot be bought by private individuals (default: false)subscription_only boolean — Only products available for recurring orders (default: false)sort string — Result ordering (default: "recommended"; one of: "recommended", "price_asc", "price_desc", "rating_desc", "review_count_desc")@type string (default: "MonotaroSearchItem")id string requiredurl string requiredname string requiredsub_name string nullablebrand string nullablebrand_id string nullableimage string nullableimages array (default: [])description string nullableusage string nullableprice number nullableprice_with_tax number nullablehas_price_range boolean nullableis_special_price boolean nullablecurrency string (default: "JPY")quantity string nullablemin_ship_days integer nullablemax_ship_days integer nullablerating number nullablereview_count integer nullablevariant_count integer nullableis_orderable boolean nullablecan_subscribe boolean nullablehas_eco_mark boolean nullablehas_rohs_mark boolean nullablecategory string nullablecategory_id string nullablebreadcrumbs array (default: [])@type string (default: "MonotaroCategoryRef")id string requiredname string requiredurl string requiredspecs object (default: {})* stringdocuments array (default: [])@type string (default: "MonotaroDocument")name string requiredurl string required422 — 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.