/geekbench/devices

POST /api/geekbench/devices

Price: 10 credits

Fetch one device's Geekbench rollup by its slug. Returns the marketing name, the model identifier the operating system reports, the processor with its frequency and core count, and the single-core, multi-core and graphics scores aggregated across every run uploaded for that device, plus the ranked comparison tables against other devices of the same family, each peer carrying its own slug so it can be fetched in turn.

How to use it

`platform` selects a separate catalogue, and the same slug does not exist in two of them, so pass the platform the slug came from rather than guessing. Android slugs are often the vendor's internal model code rather than a product name ('samsung-sm-s936n' for the Galaxy S25+), so take the slug from the Android benchmark chart instead of composing one. Scores here are the device's aggregate across all uploads, which is what to compare hardware on; a single machine's own numbers come from a CPU or GPU run instead. Which graphics score a device carries depends on its platform — Metal on Apple hardware, OpenCL or Vulkan on Android — so read the keys of `scores` rather than assuming one.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• alias string required — Device slug from a browser.geekbench.com device URL, as returned by the Android, iOS or Mac benchmark chart (examples: "iphone-17-pro-max", "samsung-sm-s936n", "macbook-pro-14-inch-2025"; minLength: 1)
• platform string required — Which device catalogue the slug belongs to: android for phones and tablets running Android, ios for iPhone and iPad, mac for Apple desktops and laptops (one of: "android", "ios", "mac")

Response

• @type string (default: "GeekbenchDevice")
• alias string required
• url string required
• platform string required
• name string required
• model_identifier string nullable
• processor string nullable
• processor_frequency_mhz integer nullable
• processor_core_count integer nullable
• single_core_score integer nullable
• multi_core_score integer nullable
• scores object (default: {})
  • * integer
• details object (default: {})
  • * string
• charts array (default: [])
  • @type string (default: "GeekbenchComparisonChart")
  • name string required
  • rows array (default: [])
    • @type string (default: "GeekbenchChartRow")
    • name string required
    • alias string nullable
    • url string nullable
    • description string nullable
    • score integer nullable
    • scores object (default: {})
      • * integer

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 — No device page exists for that slug in that catalogue 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.