/notebookcheck/rankings

POST /api/notebookcheck/rankings

Price: 10 credits

Get one editorial ranking with its ordered picks, their scores and the reasoning behind each

How to use it

This is the editors' shortlist rather than a database query, so it answers 'what should I buy' where notebookcheck/devices/search answers 'what exists'. Each place carries the editorial reasoning in `text` and the tested score in `rating`, and `review_id` points at the full review. Take ids from notebookcheck/rankings/search; an id belonging to an ordinary article resolves to 412.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• ranking string required — Notebookcheck page id of the ranking, or the full URL of its page (examples: "98628", "https://www.notebookcheck.net/Ranking-Best-gaming-laptops-reviewed-by-Notebookcheck.98628.0.html"; minLength: 1)

Response

• @type string (default: "NotebookcheckRanking")
• id string required
• url string required
• ranking_title string required
• subtitle string nullable
• abstract string nullable
• author string nullable
• published_date string nullable
• image string nullable
• update_note string nullable
• places array (default: [])
  • @type string (default: "NotebookcheckRankingPlace")
  • position integer required
  • name string required
  • review_id string nullable
  • review_url string nullable
  • rating number nullable
  • processor string nullable
  • processor_url string nullable
  • graphics_card string nullable
  • graphics_card_url string nullable
  • memory_and_storage string nullable
  • list_price string nullable
  • image string nullable
  • text string nullable
  • attributes array (default: [])
    • @type string (default: "NotebookcheckSpec")
    • name string required
    • value string required
    • url string nullable
• tags array (default: [])
• translations array (default: [])
  • @type string (default: "NotebookcheckTranslation")
  • language string required
  • url string required
• related_articles array (default: [])
  • @type string (default: "NotebookcheckPageRef")
  • id string required
  • url string required
  • page_title 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 — The page id does not exist, or it belongs to a page that is not a ranking. 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.