/notebookcheck/devices

POST /api/notebookcheck/devices

Price: 5 credits

Get one laptop, phone or tablet with its specifications and the reviews written about it elsewhere

How to use it

This is the device record, not an editorial article: `external_reviews` is the collected verdict of other outlets, each with its own publisher, language, score and abstract, which is what makes it useful for aggregate opinion on a model. Take ids from notebookcheck/devices/search rows whose `page_kind` is `device`; a row with `page_kind` `review` points at an article and resolves to 412 here. `processor_url` and `graphics_adapter_url` link the chip pages, so a specification question can be followed one hop further without a search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• device string required — Notebookcheck page id of the device, or the full URL of its page (examples: "1186020", "https://www.notebookcheck.net/Samsung-Galaxy-S26-FE-Reviews-and-Specs.1329214.0.html"; minLength: 1)

Response

• @type string (default: "NotebookcheckDevice")
• id string required
• url string required
• name string required
• series string nullable
• series_url string nullable
• summary string nullable
• published_date string nullable
• processor string nullable
• processor_url string nullable
• graphics_adapter string nullable
• graphics_adapter_url string nullable
• memory string nullable
• display string nullable
• storage string nullable
• connections string nullable
• networking string nullable
• size string nullable
• battery string nullable
• operating_system string nullable
• camera string nullable
• additional_features string nullable
• weight_kg number nullable
• price string nullable
• external_review_count integer nullable
• specs array (default: [])
  • @type string (default: "NotebookcheckSpec")
  • name string required
  • value string required
  • url string nullable
• external_reviews array (default: [])
  • @type string (default: "NotebookcheckExternalReview")
  • review_title string required
  • url string nullable
  • publisher string nullable
  • language string nullable
  • rating number nullable
  • text string nullable
  • review_type string nullable
  • length string nullable
  • date string nullable
  • is_online boolean nullable
  • scores array (default: [])
    • @type string (default: "NotebookcheckSpec")
    • name string required
    • value string required
    • url string nullable
• 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 device record. 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.