POST /api/mandarake/categories
Price: 5 credits
List the Mandarake (まんだらけ) catalogue taxonomy: the top-level departments when no category is given, otherwise the direct children of the given category. Category codes returned here drive the category_id filter of the item search endpoint. Names are available in Japanese, English and Chinese.
Walk the Mandarake category tree. Call without category_id to get the top-level departments (comics, toys, cards, doujin, idols and so on), then pass the id of any node to get its direct children; the tree is up to five levels deep and a leaf returns an empty list. Each node carries id (usable as category_id of the item search endpoint), name, url and parent_id. Set lang to ja for the original Japanese names; en and zh are machine translations.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)category_id string nullable — Category code whose children to list; omit to list the top-level ones (examples: "06")lang string — Language of the returned names (default: "en"; one of: "ja", "en", "zh")@type string (default: "MandarakeCategory")id string requiredname string requiredurl string requiredparent_id string nullable422 — Malformed category_id (a Mandarake category code has an even number of digits, e.g. '06' or '0611') 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.