Skip to main content
Affiliates can use the public REST API to display their own challenge standings on their websites. These routes are publicly documented but require a signed API key request with the view_balance permission. The API key’s user must own the challenge. Keep the secret key on your server and serve standings only to your intended audience.

Routes

Use a challenge ID from the first route when requesting its leaderboard. The list route returns 403 if the API key’s user owns no challenges. The leaderboard route returns 404 if the challenge does not exist or belongs to another affiliate, including when the caller is a participant.

Leaderboard data

The leaderboard response includes title, description, starts_at, expires_at, as_of, auto_enroll, volume, base_prize_usd, max_volume_usd, max_prize_usd, prize_pool_usd, and payouts. The data array contains one row per ranked participant: Participants are ranked by sqrt(max(volume, 0)) * max(pnl, 0). The prize pool starts at base_prize_usd and increases linearly with challenge volume until it reaches max_prize_usd at max_volume_usd. The payouts array provides the configured percentage for each winning rank; payout_usd is a projection, not a completed payment. Trade metrics include complete UTC hours only and stop advancing at challenge expiry. Use as_of to show when the standings were last calculated. Fetch fresh standings after an hour boundary rather than on every page view.

Website access

Call these routes from your website’s backend. Never put the API secret in browser code or expose the raw API response to unauthorized visitors. QFEX checks that the API caller owns the challenge; your website must restrict its displayed standings to the affiliate and the affiliate’s directly referred participants. Responses include Cache-Control: private, no-store.