/gsmarena/reviews/search

POST /api/gsmarena/reviews/search

Price: 5 credits

Walk GSMArena's editorial review index, newest first, optionally restricted to one tag. Each row carries the review id, URL, headline, subtitle, publication date, lead image and comment count.

How to use it

A chronological index with no free-text parameter: to find the review of a named device, either read that device's record, which carries its review id, or ask for a larger count and match the headlines. Tags are the source's own — brand names plus `Tablets` — they are case-insensitive, and one the source does not use returns an empty list rather than an error. The rows mix full reviews, hands-on pieces and comparisons; pass a row's id to the review endpoint for the article itself.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of reviews to return (min: 1; max: 3000)
• tag string nullable — Keep only reviews filed under this GSMArena review tag (examples: "Apple", "Tablets", "Samsung"; minLength: 1)

Response

• @type string (default: "GsmarenaReviewCard")
• id integer required
• url string required
• headline string required
• subtitle string nullable
• published string nullable
• published_at integer nullable
• image string nullable
• comments integer 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 — The entity was not found, or a precondition failed 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.