/rakuma/items/comments

POST /api/rakuma/items/comments

Price: 5 credits

Get the public comment thread under a Rakuma listing: the buyer questions and price negotiations plus the seller's replies, newest first, each with its text, author nickname, a flag marking the seller's own messages and when it was posted.

How to use it

Read the comment thread of a Rakuma listing by 32-hex id or item.fril.jp URL. Each comment has text, author, is_seller, created_at and created_at_label. Rakuma only publishes how long ago a comment was posted, so created_at is derived from that label and created_at_label keeps the original wording. Many listings have no comments at all and then the result is an empty list.

Parameters

• access-token string required

Request body

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

Response

• @type string (default: "RakumaItemComment")
• text string nullable
• author string nullable
• is_seller boolean (default: false)
• created_at integer nullable
• created_at_label 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 — Listing not found (well-formed id with no Rakuma listing) 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.