/notebookcheck/drives/search

POST /api/notebookcheck/drives/search

Price: 20 credits

Search the laptop storage benchmark database of SSDs and hard drives

How to use it

Every record is one drive as measured inside a tested machine, so RAID pairs and OEM part numbers appear as their own entries and the same retail model can show up several times with different capacities. Ordering is by performance rating, best first, unless `sort_by` is set. `query` matches manufacturer and model text only, so ask for a capacity or an interface in words rather than expecting a filter for them.

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 and model (examples: "Samsung 990", "WD Black"; minLength: 1)
• match_all_words boolean — Require every word of `query` to match; set false to match any of them (default: true)
• announced_months_ago integer nullable — Keep drives announced at least this many months ago (min: 1)
• benchmarked_only boolean — Keep only drives that carry at least one measured benchmark score (default: false)
• on_sale_only boolean — Keep only drives 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", "drive_type")
• count integer required — Max number of results (min: 1)

Response

• @type string (default: "NotebookcheckDrive")
• item_id string required
• name string required
• page_id string nullable
• url string nullable
• position integer nullable
• drive_type string nullable
• capacity_gb number nullable
• rpm integer nullable
• interface string nullable
• form_factor string 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.