/mandarake/items/search

POST /api/mandarake/items/search

Price: 20 credits

Search the Mandarake (まんだらけ) second-hand catalogue by keyword and/or category, narrowed by branch, price range, arrival window, availability, pre-order and R18 flags, ordered by arrival date, price or title. Returns item cards with the catalogue id, name, photo, branch, price, stock line and the price range of the same item at other branches. Texts are available in Japanese, English and Chinese.

How to use it

Search order.mandarake.co.jp. Give a keyword, a category_id (code such as '0611' from the categories endpoint) or both, and optionally restrict to one branch with store (a branch on its own is not a search scope and returns nothing). Narrow with price_min/price_max in JPY, arrival_window (items added in the last 6 to 72 hours), hide_sold_out, hide_adult and preorder_only; order with sort plus order. Each result carries id (usable with the items endpoint), url, name, image, store (the branch holding it) with other_store_count when the same item is at several branches, stock_number (the branch's own warehouse label, not a search input), price in JPY, stock_message, is_sold_out, is_new_arrival, is_adult and other_store_price_min/other_store_price_max. Sold-out items are returned unless hide_sold_out is set, and R18 items are returned unless hide_adult is set. Every item is a single physical second-hand copy. The source serves at most 10000 items per query. Set lang to ja for the original Japanese text; en and zh are machine translations.

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 query (examples: "ガンダム", "Dragon Ball"; minLength: 1)
• category_id string nullable — Category code to search inside, e.g. '0611' (from the categories endpoint) (examples: "0611")
• count integer required — Max number of results to return (min: 1; max: 10000)
• store string nullable — Keep only items held by this branch (one of: "nakano", "nagoya", "shibuya", "umeda", "fukuoka", "grandchaos", "lalala", "sapporo", "utsunomiya", "kokura", "complex", "nayuta", "cocoo", "kyoto", "puck2", "omiya", "sahra")
• price_min integer nullable — Minimum price in JPY (min: 0)
• price_max integer nullable — Maximum price in JPY (min: 0)
• arrival_window string nullable — Keep only items added within this window (one of: "last_6_hours", "last_12_hours", "last_18_hours", "last_24_hours", "last_72_hours")
• hide_sold_out boolean — Keep only items that are still available (default: false)
• hide_adult boolean — Drop R18 items from the results (default: false)
• preorder_only boolean — Keep only items open for pre-order (default: false)
• sort string — Result ordering (default: "arrival"; one of: "arrival", "price", "title")
• order string — Direction of the ordering (default: "desc"; one of: "asc", "desc")
• lang string — Language of the returned texts (default: "en"; one of: "ja", "en", "zh")

Response

• @type string (default: "MandarakeItemCard")
• id string required
• url string required
• name string nullable
• image string nullable
• store string nullable
• other_store_count integer (default: 0)
• stock_number string nullable
• price number nullable
• currency string (default: "JPY")
• stock_message string nullable
• is_sold_out boolean (default: false)
• is_new_arrival boolean (default: false)
• is_adult boolean (default: false)
• other_store_price_min number nullable
• other_store_price_max number nullable

Errors

• 422 — Neither keyword nor category_id was given, or a malformed category_id 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.

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.