/gsmarena/devices

POST /api/gsmarena/devices

Price: 5 credits

Return the full GSMArena specification sheet for one mobile device: name, manufacturer, official image, headline figures (release, body, software, storage, display, cameras, RAM, chipset, battery), the complete spec table grouped by section, retailer offers and the links to that device's editorial review or hands-on/preview news article, user opinions, picture gallery and GSMArena's own YouTube video review of the device, when one exists.

How to use it

Resolve one phone, tablet or smartwatch on gsmarena.com. The numeric id is what identifies the device: the slug in the URL is decorative and GSMArena serves whatever device the number points at, so passing a URL whose slug names a different model returns the model the id belongs to, not the one the slug reads like. Get ids from the device search, brand or keyword-search endpoints rather than guessing them. `specs` carries every row of the source's own table, including sections that only some devices have (`Our Tests` benchmark scores, `EU LABEL` energy-label figures), so read it instead of assuming a fixed field set. When `review_id` is null, check `news_id`: GSMArena sometimes links a hands-on or preview article in the review slot instead of a full review, and that article resolves through gsmarena/news rather than gsmarena/reviews.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• device string required — Device page URL, its `{slug}-{id}` form, or the bare numeric device id (examples: "12771", "samsung_galaxy_s24_ultra-12771", "https://www.gsmarena.com/nokia_3310-192.php"; minLength: 1)

Response

• @type string (default: "GsmarenaDevice")
• id integer required
• url string required
• name string required
• brand string nullable
• brand_id integer nullable
• image string nullable
• released string nullable
• body_highlight string nullable
• os_highlight string nullable
• storage_highlight string nullable
• display_size string nullable
• display_resolution string nullable
• main_camera_resolution string nullable
• video_resolution string nullable
• ram string nullable
• chipset string nullable
• battery_capacity string nullable
• battery_highlight string nullable
• popularity number nullable
• hits integer nullable
• fans integer nullable
• review_id integer nullable
• review_url string nullable
• news_id integer nullable
• news_url string nullable
• video_review_url string nullable
• opinions_url string nullable
• pictures_url string nullable
• price_url string nullable
• offers array (default: [])
  • @type string (default: "GsmarenaOffer")
  • variant string nullable
  • price string required
  • url string nullable
  • store_image string nullable
  • description string nullable
• specs array (default: [])
  • @type string (default: "GsmarenaSpec")
  • section string required
  • label string nullable
  • value string required
  • key 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 device 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.