POST /api/ekiten/shops/menus
Price: 5 credits
Get the menu of a shop on Ekiten (エキテン): category, name, price, description, images with captions, tags, the coupons it combines with and the staff who serve it, for each service or dish
Shop ids come from ekiten/shops/search.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)shop string required — Ekiten shop id or shop URL (examples: "7084758", "https://www.ekiten.jp/shop_7084758/"; minLength: 1)count integer required — Max number of results (min: 1; max: 1000)@type string (default: "EkitenMenu")id string requiredshop_id string requiredshop_url string requiredcategory string nullablename string nullableprice string nullabledescription string nullableimage_urls array (default: [])images array (default: [])@type string (default: "EkitenMenuImage")url string requiredcaption string nullableis_pickup boolean (default: false)tags array (default: [])coupons array (default: [])@type string (default: "EkitenCoupon")id string nullableurl string nullabletitle string nullablediscount string nullablekind string nullabletags array (default: [])is_pickup boolean (default: false)staff array (default: [])@type string (default: "EkitenStaff")id string nullableurl string nullablename string nullablename_kana string nullablerole string nullablegender string nullableage integer nullableimage string nullable422 — shop is not an Ekiten shop id or URL 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 — No Ekiten shop under that id 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.