/gsmarena/brands/devices

POST /api/gsmarena/brands/devices

Price: 5 credits

Walk the full device catalogue of one manufacturer on GSMArena, newest announcement first. Each row carries the numeric device id, page URL, name, manufacturer, model and image, plus the one-line summary GSMArena writes for the listing, with the announcement month parsed out of it.

How to use it

This is the only way to enumerate a manufacturer's whole catalogue — the device search returns a sample instead. Pass the brand id from the brands endpoint; a numeric id that is not a brand answers 412 rather than an empty list. Rows are ordered by announcement date, so a small count gives you the newest models. Feed a row's id into the device endpoint for the full specification sheet.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• brand string required — Brand page URL, its `{slug}-phones-{id}` form, or the bare numeric brand id (examples: "9", "samsung-phones-9", "https://www.gsmarena.com/apple-phones-48.php"; minLength: 1)
• count integer required — Max number of devices to return (min: 1; max: 2000)

Response

• @type string (default: "GsmarenaDeviceCard")
• id integer required
• url string required
• name string required
• brand string nullable
• model string nullable
• image string nullable
• summary string nullable
• announced string 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 — No brand exists under this id on GSMArena. 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.