/coolapk/devices/versions

POST /api/coolapk/devices/versions

Price: 1 credit

List every RAM/ROM configuration of a Coolapk phone model by its product id

How to use it

Every RAM/ROM configuration of one phone model, by product id — this is where a model's price ladder comes from, since coolapk/devices/search carries only the cheapest variant's price. The input must be a `product_id` from search, never a `config_id`: the two id spaces overlap numerically and the source does not reject a config id here — it looks up whatever product shares that number and, close to half the time, that is a real but unrelated phone, returned as an honest 200 with no way to tell it apart from a correct answer. There is no field in the response that proves the id you passed was really a product id rather than a coincidentally valid config id. Pass any config id this endpoint returns to coolapk/devices for that variant's spec sheet. Prices are China-market launch prices in CNY, and the source reports zero for models it never priced there.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product_id string required — Coolapk product id — the id of a phone model, as returned in the `product_id` field of coolapk/devices/search. This is a model id, not a config id. (examples: "4999", "5933"; minLength: 1)

Response

• @type string (default: "CoolapkDeviceVersion")
• config_id string required
• product_id string required
• config_name string required
• price number nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit 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 id not found 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 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 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 Wait at least 30 seconds, then retry.

Response 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.