/joshin/makers

POST /api/joshin/makers

Price: 20 credits

List the manufacturers stocked in one Joshin (上新電機) category, as the manufacturer names the product search accepts.

How to use it

List the manufacturers of one joshin (joshinweb.jp) category. Pass genre plus category (the numeric category id, or a full category URL, both published by the categories endpoint). Each entry carries id, which is the exact manufacturer string to pass back as maker to the product search, and name, which is the same manufacturer as Joshin renders it for display and differs from id only where the rendered label collapses a fullwidth space. Every entry also carries genre, category_id and category_url.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• genre string required — Genre the category belongs to (one of: "kaden", "season", "house", "kitchen", "health", "interior", "av", "sound", "audio", "pc", "peripheral", "supply", "mobile", "camera", "car", "diy", "outdoor", "apparel", "watch", "game", "toy", "hobby", "train", "cg", "liquor", "drug"; examples: "hobby")
• category string required — Category id inside the genre, or a full category URL (examples: "3337", "https://joshinweb.jp/hobby/3337.html"; minLength: 1)
• count integer required — Max number of manufacturers to return (min: 1)

Response

• @type string (default: "JoshinMaker")
• id string required
• name string required
• genre string required
• category_id string required
• category_url string required

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 — The genre and category id do not name a Joshin category 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.