/mandarake/items

POST /api/mandarake/items

Price: 5 credits

Get one Mandarake (まんだらけ) second-hand item by its catalogue item id or item URL: name, live price and stock, the branch that holds it, the branch's own stock number, the ten-point condition grade, category breadcrumbs, series and edition tags, the R18 flag, package size and weight, photos and the same item offered by other Mandarake branches with their prices. Texts are available in Japanese, English and Chinese.

How to use it

Fetch one Mandarake item by its catalogue item id (e.g. '1333571329', the id the search endpoint returns) or a full item URL. Returns id, url, name, image and images, store (the branch holding the item), stock_number (the branch's own warehouse label, not an input of this endpoint), price and price_with_tax in JPY, is_in_stock, condition and condition_rank (Mandarake grades used goods from 1 to 10, 10 being mint) with condition_rank_max when the branch grades a span such as '7 to 9', category, category_id (reusable as category_id of the search endpoint) and breadcrumbs, tags (series, edition and print codes, each also usable as a search keyword), is_adult (the R18 flag the search endpoint filters on with hide_adult), package_size with width_mm/height_mm/depth_mm/weight_g, description, notes and other_stores (the same item held by other branches, each with its own id that this endpoint accepts, store, price and is_sold_out). Every item is a single physical second-hand copy, so an item that is sold out is not restocked. Prices are in JPY; price is before tax and price_with_tax includes it. Set lang to ja for the original Japanese text; en and zh are machine translations, and a translated grade sometimes loses the leading number that fills condition_rank, so read grades from ja.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• item string required — Mandarake catalogue item id, or a full item URL (examples: "1333571329", "https://order.mandarake.co.jp/order/detailPage/item?itemCode=1333571329")
• lang string — Language of the returned texts (default: "en"; one of: "ja", "en", "zh")

Response

• @type string (default: "MandarakeItem")
• id string required
• url string required
• name string nullable
• image string nullable
• images array (default: [])
• store string nullable
• stock_number string nullable
• price number nullable
• price_with_tax number nullable
• currency string (default: "JPY")
• is_in_stock boolean (default: false)
• condition string nullable
• condition_rank integer nullable
• condition_rank_max integer nullable
• category string nullable
• category_id string nullable
• breadcrumbs array (default: [])
• categories array (default: [])
  • @type string (default: "MandarakeItemCategory")
  • id string required
  • name string required
  • breadcrumbs array (default: [])
• tags array (default: [])
• is_new_arrival boolean (default: false)
• is_adult boolean (default: false)
• package_size string nullable
• width_mm number nullable
• height_mm number nullable
• depth_mm number nullable
• weight_g number nullable
• description string nullable
• notes string nullable
• other_stores array (default: [])
  • @type string (default: "MandarakeOtherStoreOffer")
  • id string required
  • url string required
  • name string nullable
  • image string nullable
  • store string nullable
  • price number nullable
  • currency string (default: "JPY")
  • is_sold_out boolean (default: false)

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 — Item not found (well-formed item id but no such item on Mandarake) 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.