POST /api/smartnews/rankings
Price: 10 credits
List the ranked SmartNews+ articles — the trending ranking or the most read this week — with rank, title, publisher, publication time and image.
Pass an article id to smartnews/articles for the preview body and related articles.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)ranking string required — Which SmartNews+ ranking to return (one of: "trending", "weekly")count integer required — Max number of articles to return (min: 1)@type string (default: "SmartnewsRankedArticle")id string requiredurl string nullableshort_title string nullablesource_url string nullablepublisher string nullablepublisher_id string nullablepublisher_logo string nullablepublisher_wide_logo string nullableauthor string nullablepublished_at integer nullablediscovered_at integer nullablekind string nullableis_premium boolean nullableis_explainer boolean nullableplus_url string nullablechannel_identifier string nullablelanguage string nullableimage string nullabletopics array (default: [])@type string (default: "SmartnewsTopic")id string requiredname string nullabledisplay_name string nullablekind string nullablesubject_type string nullableimage string nullableis_featured boolean nullablevideo object nullable@type string (default: "SmartnewsVideo")id string requiredurl string nullabledescription string nullableduration integer nullableview_count integer nullablelike_count integer nullablecomment_count integer nullablepublished_at integer nullableupdated_at integer nullablechannel_name string nullablechannel_image string nullableimage string nullablevideo_type string nullablevideo_key string nullablelanguage string nullablerank integer required422 — 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.