# /monotaro/products/search

`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.

## How to use it

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.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (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 only
- `order_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":"プラス(+)"})
  - `*` (string)
- `price_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")

## Response

### 200 — Successful Response

- `@type` (string) (default: "MonotaroSearchItem")
- `id` (string, required)
- `url` (string, required)
- `name` (string, required)
- `sub_name` (string, nullable)
- `brand` (string, nullable)
- `brand_id` (string, nullable)
- `image` (string, nullable)
- `images` (array) (default: [])
- `description` (string, nullable)
- `usage` (string, nullable)
- `price` (number, nullable)
- `price_with_tax` (number, nullable)
- `has_price_range` (boolean, nullable)
- `is_special_price` (boolean, nullable)
- `currency` (string) (default: "JPY")
- `quantity` (string, nullable)
- `min_ship_days` (integer, nullable)
- `max_ship_days` (integer, nullable)
- `rating` (number, nullable)
- `review_count` (integer, nullable)
- `variant_count` (integer, nullable)
- `is_orderable` (boolean, nullable)
- `can_subscribe` (boolean, nullable)
- `has_eco_mark` (boolean, nullable)
- `has_rohs_mark` (boolean, 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 — Validation Error

The request body did not validate

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: 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

What to do: 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

What to do: 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

What to do: 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

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these 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.