/gsmarena/reviews

POST /api/gsmarena/reviews

Price: 10 credits

Return one GSMArena editorial review in full: headline, author, publication date, tags, lead image, the device it reviews, the comment thread link, and every section of the article — GSMArena splits a review across several pages and each one is returned with its heading, plain text and HTML, with the whole article also joined into a single text field.

How to use it

This is GSMArena's own long-form review, not user opinions — for those use the device opinions endpoint. Pass the numeric review id, taken from the `review_id` on the device's own record, not the device id itself: review ids and device ids are independent counters that overlap numerically in the low range, so a device id can silently resolve here to an unrelated review. Section headings name what each part covers (design, lab tests, camera, verdict), so target a section rather than reading the joined `text` when you want one aspect. Hands-on and comparison articles live in the same id space as full reviews.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• review string required — Editorial review URL, its `{slug}-review-{id}` form, or the bare numeric review id (examples: "2995", "poco_f9_ultra-review-2995"; minLength: 1)

Response

• @type string (default: "GsmarenaReview")
• id integer required
• url string required
• headline string required
• author string nullable
• published string nullable
• published_at integer nullable
• tags array (default: [])
• image string nullable
• device_id integer nullable
• device_url string nullable
• device_name string nullable
• comments integer nullable
• comments_url string nullable
• sections array (default: [])
  • @type string (default: "GsmarenaReviewSection")
  • number integer required
  • heading string required
  • url string required
  • text string (default: "")
  • html string (default: "")
• text string (default: "")

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 editorial review 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.