/rakuma/users/items

POST /api/rakuma/users/items

Price: 10 credits

List everything a Rakuma seller has on their shop page — both the listings still for sale and the ones already sold, in the order the shop shows them. Each listing comes back with its id, name, price in JPY, sold flag, brand, category, category path, seller id and image.

How to use it

Walk a Rakuma seller's inventory by 32-hex shop id or fril.jp/shop URL. Each listing has id (feed it to rakuma/items), internal_id, name, price, currency, is_sold, brand, category, category_path, seller_id, seller_type, image and url. The shop page mixes on-sale and sold listings and offers no server-side filter, so filter on is_sold yourself, or use rakuma/items/search when you need it done upstream.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• user string required — Rakuma shop id (32 hex characters) or shop URL (examples: "cd3740fcb59f2bcd8ed141125a8bd206", "https://fril.jp/shop/cd3740fcb59f2bcd8ed141125a8bd206"; minLength: 1)
• count integer required — Max number of listings to return (min: 1; max: 3600)

Response

• @type string (default: "RakumaItemCard")
• id string required
• internal_id integer nullable
• name string required
• price number nullable
• currency string (default: "JPY")
• is_sold boolean (default: false)
• brand object nullable
  • @type string (default: "RakumaBrandRef")
  • id integer required
  • name string nullable
  • url string nullable
• category object nullable
  • @type string (default: "RakumaCategoryRef")
  • id integer nullable
  • name string nullable
  • url string nullable
• category_path array (default: [])
  • @type string (default: "RakumaCategoryRef")
  • id integer nullable
  • name string nullable
  • url string nullable
• seller_id integer nullable
• seller_type string nullable
• image string nullable
• url 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 — Seller not found (well-formed id with no Rakuma shop) 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.