/rakuma/sizes

POST /api/rakuma/sizes

Price: 1 credit

List the size vocabulary Rakuma (fril.jp) uses: nine groups — women's and men's clothing and shoes, kids' and baby clothing and shoes, rings and women's underwear — each with the individual sizes and their ids. These ids are what the listing search expects for its size filter.

How to use it

Resolve Rakuma size ids. Omit size_group_id for all nine groups, or pass one to get a single group. Each group has id, name and sizes (id, name). Feed a size id into rakuma/items/search as size_id; that filter takes one size at a time. Categories tell you which group applies through size_group_id and related_size_group_ids on rakuma/categories.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• size_group_id integer nullable — Size group to return; omit to get all of them (>: 0)
• count integer required — Max number of size groups to return (min: 1)

Response

• @type string (default: "RakumaSizeGroup")
• id integer required
• name string nullable
• sizes array (default: [])
  • @type string (default: "RakumaSize")
  • id integer required
  • name string nullable

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 — Size group not found (well-formed but nonexistent size_group_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.

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.