/threedmark/leaderboards

POST /api/threedmark/leaderboards

Price: 20 credits

Read a 3DMark Hall of Fame board — the ranked best submitted runs for one benchmark, preset and score, current boards and retired ones alike. Every entry carries the full system fingerprint behind the score: the submitting user and country, the submission date, the motherboard manufacturer and model, the processor with its process node, core count and base and turbo clocks, the graphics card with its vendor, memory, core and memory clocks, driver name and version and multi-GPU arrangement, and the run's own score with its graphics and CPU components.

How to use it

This is where the hardware detail lives: the per-run pages the site links to are closed to us, so a board entry is the only route to a run's motherboard, driver version and clock readings. Boards are one per benchmark AND preset AND ranked score, so Time Spy Extreme has separate overall, graphics and CPU boards while base Time Spy only splits into overall and graphics, and comparing across boards compares different quantities. `single_gpu_only` is the right switch when the top of a board is dominated by multi-card systems. A board is the top submitted scores, so its clock readings sit far above stock — use it for what hardware has reached, and the result search for what it typically does. CPU Profile has no board here; rank processors by thread count through the result search with test=cpu_profile and the matching score type.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• leaderboard string — Which Hall of Fame board to read. Each is one benchmark, preset and ranked score, including the retired 3DMark 11, Vantage, 3DMark06, Ice Storm, Cloud Gate and Sky Diver boards (default: "time_spy"; one of: "time_spy_extreme", "time_spy_extreme_graphics_score", "time_spy_extreme_cpu_score", "time_spy", "time_spy_graphics_score", "speed_way", "port_royal", "solar_bay", "solar_bay_extreme_dx12", "solar_bay_extreme_vulkan", "steel_nomad_dx12", "steel_nomad_vulkan", "steel_nomad_light_dx12", "steel_nomad_light_vulkan", "fire_strike_ultra", "fire_strike_extreme", "fire_strike", "fire_strike_physics_score", "night_raid", "wild_life", "wild_life_extreme", "sky_diver", "cloud_gate", "ice_storm_unlimited", "ice_storm_extreme", "ice_storm", "3dmark_11_extreme", "3dmark_11_performance", "3dmark_11_entry", "3dmark_11_physics_score", "vantage_extreme", "vantage_performance", "vantage_entry", "3dmark06", "orange_room", "blue_room")
• single_gpu_only boolean — Restrict the board to single-graphics-card systems (default: false)
• count integer required — Max number of ranked runs to return (min: 1; max: 1000)

Response

• @type string (default: "ThreedmarkLeaderboardRun")
• id string required
• url string nullable
• leaderboard string required
• leaderboard_name string nullable
• rank integer required
• test_name string nullable
• test_code string nullable
• overall_score number nullable
• displayed_score string nullable
• workload_version string nullable
• is_valid boolean nullable
• is_hidden boolean nullable
• component_scores array (default: [])
  • @type string (default: "ThreedmarkLeaderboardScore")
  • key string required
  • value number nullable
  • status string nullable
• user string nullable
• country string nullable
• submitted_at integer nullable
• run_url string nullable
• motherboard string nullable
• motherboard_manufacturer string nullable
• motherboard_model string nullable
• cpu_name string nullable
• cpu_manufacturing string nullable
• cpu_core_count integer nullable
• cpu_core_clock_mhz integer nullable
• cpu_turbo_clock_mhz integer nullable
• cpu_processors_logical string nullable
• gpu_name string nullable
• gpu_vendor string nullable
• gpu_count integer nullable
• gpu_memory_mb integer nullable
• gpu_core_clock_mhz integer nullable
• gpu_memory_clock_mhz integer nullable
• gpu_driver_name string nullable
• gpu_driver_version string nullable
• gpu_multi_gpu_solution string nullable
• is_sli_enabled boolean nullable
• system_info_version string nullable
• ui_version string nullable
• result_count integer nullable
• total_result_count integer nullable
• is_hof_valid boolean nullable
• is_less_than_week_old boolean 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 — That board has no entries under the chosen filter 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.