Trader Leaderboard (Polymarket)
The canonical Polymarket trader leaderboard, ranked by profit or volume across all time. Look up any wallet's exact rank in the global ranking.
/v2/polymarket/leaderboardQuery Parameters
Market category filter. One of: OVERALL (default), POLITICS, SPORTS, CRYPTO, CULTURE, MENTIONS, WEATHER, ECONOMICS, TECH, FINANCE.
Time window. One of: DAY (default), WEEK, MONTH, ALL.
Sort key. One of: PNL (default), VOL.
Number of rows to return. Range 1-50, default 25.
Starting index in the ranking. Range 0-1000, default 0. Combined with limit, list iteration is bounded to rank ~1050.
Optional. 0x-prefixed wallet address — returns the single row at that wallet's rank in the global ranking. Use this to look up ranks beyond the pagination cap.
Optional. Single-user lookup by Polymarket username.
Response Schema
Echoed back: market category filter applied.
Echoed back: time window applied (DAY/WEEK/MONTH/ALL).
Echoed back: sort key (PNL or VOL).
Echoed back: max rows requested.
Echoed back: starting index in the global ranking.
Number of rows returned in this response.
Ranked rows. Same data Polymarket's own UI displays.
Global rank position for the (category, time_period, order_by) tuple.
Trader's Polygon wallet address (0x-prefixed).
Display name on Polymarket. Often the wallet address itself when no custom username has been set.
Linked X/Twitter username if the trader has connected one.
Whether Polymarket has issued a verified badge for the trader.
Profile image URL if set.
Trading volume (USD) for the selected period.
Profit and loss (USD) for the selected period.
Response metadata.
Data source identifier.
List iteration is capped near rank 1050. Pass ?user= for deeper rank lookups.
Error Responses
All errors return the same envelope. The code field is stable and programmatically branchable; error and message are human-readable. errors[] is present only on validation failures with field-level detail. See the full error code reference →
Always `false` on error responses.
Short, human-readable title (e.g. 'Invalid API Key.').
Human-readable explanation for the error. Safe to surface in UIs.
Stable, hierarchical machine-readable code (e.g. 'validation.invalid_enum'). Use for programmatic handling.
Link to this code's entry in the Error Reference.
Optional. Present only on validation failures with field-level detail.
Name of the offending parameter.
Field-level machine code.
Human-readable explanation.
Authentication
API Key
To secure your requests, we strongly recommend passing your API key via the X-API-Key header. This prevents sensitive keys from being exposed in access logs or browser history.
X-API-Key: pmx_test_5e8f...Rate Limits
API rate limits are enforced based on the tier associated with your API key. Limits are tracked on two dimensions: requests per second and requests per month. Each completed request counts toward the global monthly quota. Separate endpoint-group monthly limits (matched markets, arbitrage, EV) only advance when the response body has success: true.
Usage is returned on responses via headers such as:
X-RateLimit-Limit-Second: 10X-RateLimit-Remaining-Second: 9X-RateLimit-Limit-Month: 1000X-RateLimit-Remaining-Month: 842Example (endpoint-group, when applicable)X-RateLimit-Limit-Arb-Month: 500X-RateLimit-Remaining-Arb-Month: 412If you exceed a rate limit, the API returns a 429 status with a Retry-After header indicating when you can resume.
Request
Live API Key
Parameters
Response
—Click EXECUTE to send a request →