# /iosys/products/junk

`POST /api/iosys/products/junk`

Price: 5 credits

Search the Iosys (イオシス) junk stock, the faulty and broken phones, tablets, feature phones, computers and accessories the shop sells over the counter only. Each listing carries its price, grade, the fault the shop recorded, the accessories that came with it, the specification of the model, the arrival date and which branches physically hold it.

## How to use it

Search the junk inventory of iosys.co.jp, the stock graded below the shop's used ranks and sold over the counter only. Every filter is optional, so count alone walks the whole junk stock. Narrow with keyword (matches the listing name), condition, category_id, genre_id and brand_id (the ids the catalogue endpoints report as category_id, genre_id and brand_id), and store_id to keep only what one branch holds. Order with sort. Each result carries id, url, name, price, stock, condition as the shop's own grade label, warranty, accessories, note (the fault the shop recorded, often just a pointer to a label on the unit itself), spec_text and spec, arrived_at, the category, genre and brand as both name and id, and stores, one entry per branch with its own stock count. These listings cannot be ordered online and are not reachable from the catalogue search. Prices are tax-included JPY.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `keyword` (string, nullable) — Free-text search over the junk listing name (examples: "iPhone"; minLength: 1)
- `count` (integer, required) — Max number of junk listings to return (min: 1)
- `condition` (string, nullable) — Keep only listings of this grade: rank_d is faulty but working, junk is sold as broken (one of: "rank_d", "junk")
- `category_id` (string, nullable) — Catalogue category id, as a product reports it (examples: "1", "6")
- `genre_id` (string, nullable) — Genre id, as a product reports it (examples: "6", "1")
- `brand_id` (string, nullable) — Manufacturer id, as a product reports it (examples: "18", "9")
- `store_id` (string, nullable) — Keep only listings held by this branch, as a listing reports it in stores (examples: "8")
- `sort` (string) — Result ordering (default: "arrival_desc"; one of: "arrival_desc", "stock_desc", "price_asc")

## Response

### 200 — Successful Response

- `@type` (string) (default: "IosysJunkProduct")
- `id` (string, required)
- `url` (string, required)
- `name` (string, nullable)
- `image` (string, nullable)
- `thumbnail` (string, nullable)
- `price` (number, nullable)
- `currency` (string) (default: "JPY")
- `stock` (integer, nullable)
- `condition` (string, nullable)
- `warranty` (string, nullable)
- `warranty_id` (string, nullable)
- `accessories` (string, nullable)
- `note` (string, nullable)
- `spec_text` (string, nullable)
- `spec` (object) (default: {})
  - `*` (string)
- `arrived_at` (string, nullable)
- `category` (string, nullable)
- `category_id` (string, nullable)
- `genre` (string, nullable)
- `genre_id` (string, nullable)
- `brand` (string, nullable)
- `brand_id` (string, nullable)
- `stores` (array) (default: [])
  - `@type` (string) (default: "IosysJunkStock")
  - `store_id` (string, required)
  - `store` (string, nullable)
  - `stock` (integer, 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

The entity was not found, or a precondition failed

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.