/notebookcheck/processors

POST /api/notebookcheck/processors

Price: 10 credits

Get the full specification and benchmark record of one processor

How to use it

Use this once you already have a processor page id, for example from notebookcheck/processors/search or from the processor link on a device record. The id space is shared with every other page on the site, so an id belonging to a graphics card, a device or an article resolves to 412 rather than to a neighbouring chip. Pass the numeric id or the page URL, whichever you have; the decorative slug in the URL is ignored. The `benchmarks` list is the measured score per test suite, while `specs` mirrors the vendor specification table verbatim and is the place to look for anything the typed fields do not cover.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• processor string required — Notebookcheck page id of the processor, or the full URL of its page (examples: "796971", "https://www.notebookcheck.net/AMD-Ryzen-Threadripper-PRO-7995WX-Processor-Benchmarks-and-Specs.796971.0.html"; minLength: 1)

Response

• @type string (default: "NotebookcheckProcessor")
• id string required
• url string required
• name string required
• item_id string nullable
• codename string nullable
• series string nullable
• clock_mhz number nullable
• turbo_clock_mhz number nullable
• l1_cache string nullable
• l2_cache string nullable
• l3_cache string nullable
• cores integer nullable
• threads integer nullable
• tdp_watt number nullable
• process_nm number nullable
• die_size string nullable
• max_temperature_c number nullable
• socket string nullable
• instruction_set string nullable
• is_64_bit boolean nullable
• features array (default: [])
• graphics_card string nullable
• starting_price string nullable
• announcement_date string nullable
• performance_rating number nullable
• specs array (default: [])
  • @type string (default: "NotebookcheckSpec")
  • name string required
  • value string required
  • url string nullable
• benchmarks array (default: [])
  • @type string (default: "NotebookcheckChipBenchmark")
  • name string required
  • suite string nullable
  • value number nullable
  • unit string nullable
  • percentile number nullable
  • min_value number nullable
  • avg_value number nullable
  • max_value number nullable
  • lower_is_better boolean nullable
• series_processors array (default: [])
  • @type string (default: "NotebookcheckPageRef")
  • id string required
  • url string required
  • page_title string nullable
• surrounding_processors array (default: [])
  • @type string (default: "NotebookcheckPageRef")
  • id string required
  • url string required
  • page_title string nullable
• reviews 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 processor. 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.