/notebookcheck/articles

POST /api/notebookcheck/articles

Price: 20 credits

Get the full text of one news story, review or editorial article

How to use it

Take ids from notebookcheck/articles/search, or from a device search row whose `page_kind` is `review`. `article_type` tells you which shape you got: a `review` carries the editorial verdict in `rating`, `pros` and `cons`, while `news` and other articles leave those empty, so do not read an absent rating as a bad one. `text` is the whole body including the measurement sections of a review, which can run to tens of thousands of characters.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• article string required — Notebookcheck page id of the article, or the full URL of its page (examples: "1380978", "https://www.notebookcheck.net/Lenovo-Legion-5-15IAX11-review-Optimized-for-1440p-gaming.1380978.0.html"; minLength: 1)

Response

• @type string (default: "NotebookcheckArticle")
• id string required
• url string required
• article_title string required
• article_type string required
• subtitle string nullable
• abstract string nullable
• text string nullable
• author string nullable
• published_date string nullable
• image string nullable
• rating number nullable
• rating_label string nullable
• reviewed_device string nullable
• review_category string nullable
• rating_version string nullable
• pros array (default: [])
• cons array (default: [])
• 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 an article. 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.