From zero to signal.

Make your first request in a few lines of code.

Base URL: https://api.fomo-api.com

01 Create an API key

Open API keys in your dashboard and create a key for your application. Copy the secret immediately — it is shown only once. Demo keys do not authenticate real requests.

02 Authenticate your requests

Send your key in the Authorization header. Keep it on your server, outside browser bundles and version control.

Authorization: Bearer <API_KEY>

03 Get the leaderboard

Rank wallets by realized PnL. Supported windows: 24h, 7d, and 30d. Use limit (1–200, default 50) and cursor for pagination.

curl "https://api.fomo-api.com/v1/leaderboard?window=30d" \
 -H "Authorization: Bearer <API_KEY>"

{
 "window": "30d",
 "data": [
 {
 "rank": 1,
 "address": "7xKXtg2CW87d97TXJSDpbD5jBkheTqA83TZRuJosgAsU",
 "realizedPnlUsd": 284392.00,
 "returnPct": 342.8,
 "coveragePct": 98.6
 }
 ]
}

Results contain rank, address, realizedPnlUsd, returnPct, volumeUsd, trades, coveragePct, and pnlStatus. The top-level capturedAt is the snapshot update time. Metrics may be null; null does not mean zero.

04 Look closer at a wallet

Pass a Solana wallet address to retrieve its performance. The initial contract uses a 30-day window.

curl "https://api.fomo-api.com/v1/wallet/7xKXtg2CW87d97TXJSDpbD5jBkheTqA83TZRuJosgAsU" \
  -H "Authorization: Bearer <API_KEY>"

05 Get a wallet's individual trades

The trade-level feed behind a wallet's aggregate stats: every individual swap, newest first. Use limit (1–200, default 50) and offset for pagination.

curl "https://api.fomo-api.com/v1/wallet/7xKXtg2CW87d97TXJSDpbD5jBkheTqA83TZRuJosgAsU/trades?limit=50" \
  -H "Authorization: Bearer <API_KEY>"

Each entry contains txHash, blockTime, tokenIn / tokenOut (each with chain, address, and raw amount), venue, and source. The top-level total is the wallet's full trade count, independent of the current page.

06 Check plans & limits

Public and unauthenticated. Returns the current pricing plans — id, name, priceMonthly, calls (monthly quota), rateLimit (requests per minute), description, and features — plus top-level currency, usageUnit, and periodResets. This is the source of truth for quota and rate-limit numbers; use it instead of hardcoding plan limits.

Errors & rate limits

Handle 401 for missing or invalid keys, 403 for unavailable plan features, 404 for unknown wallets, and 429 for rate or quota limits. Respect the Retry-After header. Server failures return 5xx; use bounded exponential backoff.