# /coolapk/devices

`POST /api/coolapk/devices`

Price: 10 credits

Get the full spec sheet of one Coolapk phone configuration by its config id

## How to use it

The full labelled spec sheet of one phone RAM/ROM configuration, by config id. The input must be a `config_id` from coolapk/devices/search or coolapk/devices/versions, never a product/model id: the two id spaces overlap numerically and a model id passed here quietly resolves to a different phone instead of failing — `4999` is a Huawei configuration, while product `4999` is the iPhone 17 Pro Max. Specs arrive as the source's own groups and sub-groups of title/value pairs with Chinese titles, and the first group is the source's summary, repeating values from the detailed groups below it. A measured quantity keeps its unit apart from the value, so read them together. For the same phone's other configurations and their prices, use coolapk/devices/versions with the product id.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `config_id` (string, required) — Coolapk config id — the id of one RAM/ROM variant of a phone, as returned in the `config_id` field of coolapk/devices/search and coolapk/devices/versions. This is a config id, not a product/model id: the two id spaces overlap numerically and a model id resolves to a different device. (examples: "7520", "4999"; minLength: 1)

## Response

### 200 — Successful Response

- `@type` (string) (default: "CoolapkDeviceDetail")
- `config_id` (string, required)
- `config_name` (string, required)
- `spec_groups` (array) (default: [])
  - `@type` (string) (default: "CoolapkSpecGroup")
  - `name` (string, required)
  - `items` (array) (default: [])
    - `@type` (string) (default: "CoolapkSpecItem")
    - `id` (string, nullable)
    - `value` (string, nullable)
    - `unit` (string, nullable)
    - `addition` (string, nullable)
    - `subgroup` (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

Config id not found

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.