# /pckoubou/products

`POST /api/pckoubou/products`

Price: 5 credits

Get full PC Koubou (パソコン工房) product details by product id or product URL: name, catch copy and marketing copy, maker with the maker's own product page, model number, JAN code, tax-included and tax-excluded price, reward points, shipping fee, dispatch promise and dispatch source, category trail, photos, the specification table, stock flag, merchandising labels, the average rating with the review count, and for second-hand stock the condition note, bundled accessories, warranty and the branch that holds it with its address and phone.

## How to use it

Fetch one product from pc-koubou.jp by its numeric product id (e.g. '1130453') or a full product URL. The same id space covers built-to-order machines, DIY parts, peripherals and second-hand gear: is_used says which, and a second-hand item also carries store, store_address, store_phone, condition_note, accessories and warranty. Returns name, headline, summary, description and details, maker, maker_id and maker_url (the manufacturer's own page for the product, which about two thirds of the products have), model_number, jan, price with price_without_tax, and original_price with is_discounted while a campaign runs, points and point_rate, keywords, promotion_notes, release_date with the raw release_date_text, shipping_fee_text, delivery_message, fulfilled_by, breadcrumbs with department, category, category_path and category_paths, image and images (every photo of the product gallery), specs, in_stock, labels, campaign_tags, shipping_labels, badges, purchase_limit (how many one customer may buy), purchase_note, rating and review_count, listed_at (when the shop listed the product) and updated_at, both unix seconds. Prices are in JPY; price is tax-included. The review bodies are on the products/reviews endpoint. A handful of products are sold only to business accounts: the shop hides their page from a visitor, so those come back with the catalogue fields alone and no storefront wording.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `product` (string, required) — PC Koubou product id or a full product URL (examples: "1130453", "https://www.pc-koubou.jp/products/detail.php?product_id=1130453")

## Response

### 200 — Successful Response

- `@type` (string) (default: "PckoubouProduct")
- `id` (string, required)
- `url` (string, required)
- `name` (string, nullable)
- `summary` (string, nullable)
- `description` (string, nullable)
- `maker` (string, nullable)
- `maker_id` (string, nullable)
- `maker_url` (string, nullable)
- `model_number` (string, nullable)
- `jan` (string, nullable)
- `price` (number, nullable)
- `price_without_tax` (number, nullable)
- `original_price` (number, nullable)
- `currency` (string) (default: "JPY")
- `is_discounted` (boolean) (default: false)
- `point_rate` (number, nullable)
- `keywords` (array) (default: [])
- `promotion_notes` (array) (default: [])
- `department` (string, nullable)
- `category` (string, nullable)
- `category_path` (string, nullable)
- `category_paths` (array) (default: [])
- `image` (string, nullable)
- `images` (array) (default: [])
- `specs` (object) (default: {})
  - `*` (string)
- `is_used` (boolean) (default: false)
- `in_stock` (boolean) (default: false)
- `store` (string, nullable)
- `labels` (array) (default: [])
- `campaign_tags` (array) (default: [])
- `shipping_labels` (array) (default: [])
- `rating` (number, nullable)
- `purchase_limit` (integer, nullable)
- `listed_at` (integer, nullable)
- `updated_at` (integer, nullable)
- `headline` (string, nullable)
- `details` (string, nullable)
- `breadcrumbs` (array) (default: [])
- `release_date` (string, nullable)
- `release_date_text` (string, nullable)
- `points` (integer, nullable)
- `shipping_fee_text` (string, nullable)
- `delivery_message` (string, nullable)
- `fulfilled_by` (string, nullable)
- `badges` (array) (default: [])
- `condition_note` (string, nullable)
- `accessories` (string, nullable)
- `warranty` (string, nullable)
- `store_address` (string, nullable)
- `store_phone` (string, nullable)
- `review_count` (integer, nullable)
- `purchase_note` (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

Product not found (well-formed product id but no such product on pc-koubou.jp)

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.