# /rakuma/items

`POST /api/rakuma/items`

Price: 5 credits

Get one Rakuma (fril.jp) listing by its id or URL: name, price in JPY, sold state, full description, all photos, item condition, size, brand, the three-level category path, shipping terms (who pays, method, estimated dispatch time, region it ships from), anonymous-shipping, instant-purchase and outlet flags, authenticity-check status, trust badges, like and comment counts, and the seller with shop id, names, individual-or-business type, verification badge and good/normal/bad transaction review counts. Sold listings stay public with their final price, so this doubles as a source of completed-sale comparables, although the source drops the size row from a listing once it sells.

## How to use it

Fetch a single Rakuma listing by 32-hex id or item.fril.jp URL. Returns id, internal_id, name, price, currency (always JPY), is_sold, description, image/images, condition, size, brand (id/name/url), category and category_path, shipping_payer, shipping_method, shipping_days, shipping_from, is_postage_included, is_anonymous_shipping, is_instant_purchase, is_outlet, authenticity_status, badges, like_count, comment_count, seller (id, internal_id, name, shop_name, seller_type, is_verified, image, good/normal/bad_review_count, profile_url), created_at and url. Once a listing sells, the source stops publishing its size, its like_count and its comment_count, so those are null on every sold listing no matter the category. Numeric ids from search results are not accepted here — use the 32-hex id. Use rakuma/items/comments for the negotiation thread and rakuma/users for the full seller profile.

## 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)

## Response

### 200 — Successful Response

- `@type` (string) (default: "RakumaItem")
- `id` (string, required)
- `internal_id` (integer, nullable)
- `name` (string, required)
- `price` (number, nullable)
- `currency` (string) (default: "JPY")
- `is_sold` (boolean) (default: false)
- `description` (string, nullable)
- `image` (string, nullable)
- `images` (array) (default: [])
- `condition` (string, nullable)
- `size` (string, nullable)
- `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)
- `shipping_payer` (string, nullable)
- `shipping_method` (string, nullable)
- `shipping_days` (string, nullable)
- `shipping_from` (string, nullable)
- `is_postage_included` (boolean) (default: false)
- `is_anonymous_shipping` (boolean) (default: false)
- `is_instant_purchase` (boolean) (default: false)
- `is_outlet` (boolean) (default: false)
- `authenticity_status` (string, nullable)
- `badges` (array) (default: [])
- `like_count` (integer, nullable)
- `comment_count` (integer, nullable)
- `seller` (object, nullable)
  - `@type` (string) (default: "RakumaItemSeller")
  - `id` (string, nullable)
  - `internal_id` (integer, nullable)
  - `name` (string, nullable)
  - `shop_name` (string, nullable)
  - `seller_type` (string, nullable)
  - `is_verified` (boolean) (default: false)
  - `image` (string, nullable)
  - `good_review_count` (integer, nullable)
  - `normal_review_count` (integer, nullable)
  - `bad_review_count` (integer, nullable)
  - `profile_url` (string, nullable)
- `created_at` (integer, nullable)
- `url` (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

Listing not found (well-formed id with no Rakuma listing)

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.