Leaderboards · rankings · seasons

A leaderboard API that does more than return the global top 10.

Create boards with best, replace or sum scoring; read top and around-player standings; keep seasons; and move competitive score submission behind a trusted server token when cheating matters.

Board policy
key: weekly_wins
sort_order: desc
update_strategy: sum
reset_schedule: weekly

reads:
  top
  player standing
  around player
Verify before you integrate

Verify the ranking surface in the API contract.

The OpenAPI spec documents board creation, score submission, top rankings, player standing and around-player endpoints. For a competitive board, inspect the credential boundary as carefully as the ranking features.

Live API status

A live check of the hosted API right now. No made-up uptime percentage and no hidden demo environment.

Check current status

Public API contract

The hosted HTTP surface is documented as OpenAPI. Inspect the wire format before choosing an SDK or writing an adapter.

Open the spec

MIT client SDKs

The JavaScript, Godot, Unity, and Roblox client SDK source is public. The hosted backend itself remains a managed proprietary service.

Inspect the SDK source

Documented exit path

Read what is exportable today and the written commitment for advance notice plus an export window if the hosted service winds down.

Read the exit guarantee

Score validation guide

Player-side score submission is convenient; trusted server-side submission is the safer boundary when scores unlock rewards or status.

Harden score submission
01

Choose score semantics

best keeps the better result, replace takes the latest value, and sum adds each accepted submission to the player total. Optional min/max bounds apply to the submitted value, not to the accumulated total.

02

Rank around the player

Global top lists are only one view. Fetch the player standing and nearby ranks for the surface players return to.

03

Keep trust server-side

For competitive boards, let the authoritative game server decide the result and submit with a server token instead of trusting client claims.

Fastest proof

Create one board, submit three scores, query around one player.

That test exercises the ranking behavior you will actually ship and exposes whether your score-authority model is safe enough before you wire UI around it.