/gsmarena/news

POST /api/gsmarena/news

Price: 1 credit

Return one GSMArena news article: headline, author, publication date, editorial tags, the article body as plain text and as HTML, every inline image, the link to its comment thread, and the ids of the devices the article links to.

How to use it

Pass the numeric news id; the slug in a GSMArena URL is decorative and the id decides which article is served. `linked_device_ids` are the devices the editors linked inside the body, which is the reliable way to connect an article to catalogue entries — the tags are broad topics like `Rumors` or a brand name, not device references. Read `text` for the prose and `html` when you need the markup.

Parameters

• access-token string required

Request body

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

Response

• @type string (default: "GsmarenaNewsArticle")
• id integer required
• url string required
• headline string required
• author string nullable
• author_id integer nullable
• published string nullable
• published_at integer nullable
• tags array (default: [])
• image string nullable
• text string required
• html string required
• images array (default: [])
• linked_device_ids array (default: [])
• comments_url 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 news article 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.