/gsmarena/devices/opinions

POST /api/gsmarena/devices/opinions

Price: 10 credits

Return the user opinions published under one GSMArena device, newest first, walking the source's pages. Each opinion carries its id, author name and profile id when the author is registered, the coarse anonymised location GSMArena shows, the posting date, the text, the vote count, and the author, date and text of the post it replies to.

How to use it

These are visitor comments on a device page, not scored reviews — there is no rating, so do not treat them as one. Most authors post as Anonymous and `location` is a short obfuscated token rather than a place name, so neither identifies a person. A reply quotes its parent, and the quoted text is split out into the `reply_to_*` fields so `text` holds only what this author wrote. Pass the numeric device id from the device or search endpoints.

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", "https://www.gsmarena.com/samsung_galaxy_s24_ultra-12771.php"; minLength: 1)
• count integer required — Max number of opinions to return (min: 1; max: 1000)

Response

• @type string (default: "GsmarenaOpinion")
• id integer required
• device_id integer required
• author string required
• author_id integer nullable
• location string nullable
• posted string nullable
• posted_at integer nullable
• text string required
• votes integer nullable
• reactions string nullable
• image string nullable
• reply_to_author string nullable
• reply_to_posted string nullable
• reply_to_text 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.