/notebookcheck/graphics_cards/search

POST /api/notebookcheck/graphics_cards/search

Price: 20 credits

Search the graphics card benchmark database by segment, integration, audience, age and free text

How to use it

Reach for this to rank graphics cards on measured synthetic scores; ordering is by performance rating, best first, unless `sort_by` is set. Laptop, desktop and phone parts of one brand name are separate records, so set `segment` whenever the question is about a form factor. SLI and CrossFire entries are mixed in with the rest, so use `configuration` to isolate or exclude them. For per-game frame rates pass `page_id` to notebookcheck/graphics_cards.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string nullable — Free text matched against manufacturer, model, series and codename (examples: "RTX 5070", "Radeon 890M"; minLength: 1)
• match_all_words boolean — Require every word of `query` to match; set false to match any of them (default: true)
• segment string — Device class the graphics card is built for (default: "all"; one of: "all", "laptop", "desktop", "smartphone_and_tablet", "laptop_and_desktop")
• audience string — Consumer cards, professional CAD cards, or both (default: "any"; one of: "any", "professional", "consumer")
• integration string — Integrated graphics, dedicated cards, or both (default: "any"; one of: "any", "integrated", "dedicated")
• configuration string — Single-GPU records, multi-GPU records, or both (default: "any"; one of: "any", "single", "multiple")
• directx_12_only boolean — Keep only cards that support DirectX 12 (default: false)
• announced_months_ago integer nullable — Keep cards announced at least this many months ago (min: 1)
• benchmarked_only boolean — Keep only cards that carry at least one measured benchmark score (default: false)
• on_sale_only boolean — Keep only cards the site still lists as available rather than archived (default: false)
• sort_by string nullable — Order the result by this attribute instead of by performance rating (one of: "name", "architecture", "pixel_shaders", "vertex_shaders", "core_speed", "boost_speed", "memory_speed", "memory_bus", "memory_type")
• count integer required — Max number of results (min: 1)

Response

• @type string (default: "NotebookcheckGraphicsCardListing")
• item_id string required
• name string required
• page_id string nullable
• url string nullable
• position integer nullable
• codename string nullable
• architecture string nullable
• pixel_shaders integer nullable
• vertex_shaders integer nullable
• core_speed_mhz number nullable
• shader_speed_mhz number nullable
• boost_speed_mhz number nullable
• memory_speed_mhz number nullable
• memory_bus_bit integer nullable
• memory_type string nullable
• max_memory_mb number nullable
• ai_tops_int8 number nullable
• is_integrated boolean nullable
• directx string nullable
• opengl string nullable
• process_nm number nullable
• performance_rating number nullable
• performance_percent number nullable
• benchmarks array (default: [])
  • @type string (default: "NotebookcheckBenchmark")
  • name string required
  • value number nullable
  • sample_count integer 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 entity was not found, or a precondition failed 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.