# /paypayfleamarket/users/reviews

`POST /api/paypayfleamarket/users/reviews`

Price: 1 credit

List the feedback a Yahoo!フリマ (formerly PayPay フリマ) member received: the verdict, the free-text comment, who left it and whether they were the buyer or the seller in that deal, and when it was posted. Can be narrowed to positive, neutral or negative feedback only.

## How to use it

Read the feedback texts left for a Yahoo!フリマ / PayPay フリマ member for trust analysis. Provide user (id such as 'p58634' or a profile URL) and count; optionally score (good/normal/bad). Each result has author_id/author_name/author_image/author_url of the counterparty, author_role (winner when they bought from this member), score, text and created_at (unix seconds). Counterparty names are published in full while the member's own nickname is masked. A few entries are published without a counterparty at all — they still carry the verdict and count towards the aggregate rating, and come back with author_id null. For the aggregate rating use paypayfleamarket/users.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `user` (string, required) — Yahoo!フリマ user id or a full profile URL whose feedback is returned (examples: "p58634", "https://paypayfleamarket.yahoo.co.jp/user/p58634"; minLength: 1)
- `score` (string, nullable) — Only feedback carrying this verdict (one of: "good", "normal", "bad")
- `count` (integer, required) — Max number of feedback entries to return (examples: 50; min: 1)

## Response

### 200 — Successful Response

- `@type` (string) (default: "PaypayfleamarketUserReview")
- `author_id` (string, nullable)
- `author_url` (string, nullable)
- `author_name` (string, nullable)
- `author_image` (string, nullable)
- `author_role` (string, nullable)
- `score` (string, nullable)
- `text` (string, nullable)
- `created_at` (integer, nullable)
- `item_type` (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

User not found (well-formed id but no such member on Yahoo!フリマ)

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.