Competition

My competition entry

Changed on

Get the caller's own leaderboard row and stats.

get/v1/competitions/{slug}/leaderboard/me

Request

Path parameters

slugstring required

Query parameters

walletstring
trackstring

Optional reward track, matching the board's track: empty for the primary track, otherwise one of the tracks the competition's scoring_config lists (roi | volume | oi). It decides which track's rank and reward eligibility this response describes, since a wallet holds a different position in each. There is no sort_by here: one row is not a table to re-sort.

Response

A successful response.

registeredboolean
qualifiedboolean

Reward eligibility on the track named by the request's track. Tracks can differ: the primary track may carry a minimum-volume requirement the volume track does not.

total_reward_usdstring

This wallet's payout in human USD; "0" when it earned nothing.

For a competition whose scoring_config carries a reward_schedule, this is recomputed every cycle from the wallet's track shares and the pool its cohort volume has reached, so while the competition is running it is a projection of what the wallet would be paid if the window closed now — it moves as the cohort trades, and settles once end_ts has passed. For every other competition it is the final figure, loaded after the fact, and "0" until it is.

deposits_usdstring

The wallet's deposits inside the competition window, human USD. Paired with the competition's min_deposit_usd gate — carried in scoring_config, readable via GET /v1/competitions/{slug} — to show progress toward reward eligibility. "0" when the wallet has not deposited.

Summed live, so a deposit shows up here immediately rather than at the next recompute. That is what makes it useful for gate progress and also what makes it briefly disagree with row.deposits_usd, which is the recompute-time figure qualified was decided from. Answered for wallets with no scored row too.

Changes