/notebookcheck/graphics_cards

POST /api/notebookcheck/graphics_cards

Price: 20 credits

Get the full specification, synthetic benchmarks and per-game frame rates of one graphics card

How to use it

Use this when a question is about real frame rates: `game_benchmarks` holds one entry per game and quality preset, each with the measured fps of every laptop the site tested, so it answers 'can this GPU run X at 1440p' directly instead of by inference from synthetic scores. The id space is shared across the whole site, so an id belonging to a processor, a device or an article resolves to 412. Laptop and desktop variants of the same model are separate records with separate ids.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• graphics_card string required — Notebookcheck page id of the graphics card, or the full URL of its page (examples: "934947", "https://www.notebookcheck.net/Nvidia-GeForce-RTX-5090-Laptop-Benchmarks-and-Specs.934947.0.html"; minLength: 1)

Response

• @type string (default: "NotebookcheckGraphicsCard")
• id string required
• url string required
• name string required
• item_id string nullable
• codename string nullable
• architecture string nullable
• pipelines string nullable
• tmus integer nullable
• rops integer nullable
• raytracing_cores string nullable
• tensor_cores string nullable
• core_speed string nullable
• theoretical_performance string nullable
• cache string nullable
• memory_speed string nullable
• memory_bus_width string nullable
• memory_type string nullable
• max_memory string nullable
• shared_memory string nullable
• memory_bandwidth string nullable
• api string nullable
• power_consumption string nullable
• process_nm number nullable
• pcie string nullable
• displays string nullable
• notebook_size string nullable
• predecessor 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
• game_benchmarks array (default: [])
  • @type string (default: "NotebookcheckGameBenchmark")
  • game string required
  • release_year integer nullable
  • quality string nullable
  • resolution string nullable
  • preset string nullable
  • results array (default: [])
    • @type string (default: "NotebookcheckGameResult")
    • device string nullable
    • device_url string nullable
    • cpu string nullable
    • gpu string nullable
    • fps number nullable
    • min_fps number nullable
• series_graphics_cards 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 graphics card. 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.