# /rakuma/users/reviews

`POST /api/rakuma/users/reviews`

Price: 10 credits

Read the transaction feedback left for a Rakuma seller: the verdict line, the free-text comment, who wrote it, their avatar and the date, newest first. Feedback can be narrowed to what the user received as a seller or as a buyer, and to good, neutral or bad ratings only. Rakuma publishes the latest 100 entries.

## How to use it

Fetch Rakuma seller feedback by 32-hex shop id or fril.jp/shop URL. role picks all, as_seller or as_buyer; rating picks all, good, normal or bad. Each review has rating, verdict, text, author, author_image, created_at and created_at_label. Rakuma only keeps the latest 100 entries per role, and many entries have an empty text because the rater left no comment. Aggregate counts live on rakuma/users (rating, rating_count) and rakuma/items (seller good/normal/bad_review_count).

## 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)
- `role` (string) — Whether to read the feedback this user got as a seller, as a buyer or both (default: "all"; one of: "all", "as_seller", "as_buyer")
- `rating` (string) — Keep only feedback of this rating (default: "all"; one of: "all", "good", "normal", "bad")
- `count` (integer, required) — Max number of reviews to return (min: 1; max: 100)

## Response

### 200 — Successful Response

- `@type` (string) (default: "RakumaUserReview")
- `rating` (string, nullable)
- `verdict` (string, nullable)
- `text` (string, nullable)
- `author` (string, nullable)
- `author_image` (string, nullable)
- `created_at` (integer, nullable)
- `created_at_label` (string, nullable)

## Errors

### 422 — Validation Error

The request body did not validate

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: 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)

What to do: 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

What to do: 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

What to do: 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

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these 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.