Solana token API
Prices, charts, trades, holders, wallets and new launches on Solana, over REST or one live WebSocket.
Aurelia reads every block of Solana itself, decodes the swaps of the protocols below and serves them through one API. Name the chain as solana. The same endpoints answer on every listed chain, so your code stays the same when you add another.
What is indexed
| Kind | Names |
|---|---|
| DEXes | pump.fun, PumpSwap, Raydium AMM v4, CPMM, CLMM and LaunchLab, Orca Whirlpool, Meteora DLMM, DAMM v2 and DBC |
| Launchpads | pump.fun (pumpfun), LetsBonk (letsbonk), Raydium LaunchLab (raydium-launchlab), Meteora DBC (meteora-dbc) |
Trades, candles, stats, positions and PnL cover every swap of these since indexedSince, and each answer states what it covers. How far behind the tip indexing is, is always public: GET /chains.
Addresses
Addresses are base58 and case-sensitive. Native SOL has the address native wherever a token object names it, and prices as wrapped SOL.
First requests
Everything about one token:
curl -s -H 'Authorization: Bearer <key>' 'https://app.aurelia.build/api/tokens/solana/So11111111111111111111111111111111111111112'
Its hourly candles:
curl -s -H 'Authorization: Bearer <key>' 'https://app.aurelia.build/api/tokens/solana/So11111111111111111111111111111111111111112/candles?res=1h¤cy=usd'
Its newest trades:
curl -s -H 'Authorization: Bearer <key>' 'https://app.aurelia.build/api/trades?chain=solana&token=So11111111111111111111111111111111111111112&limit=10'
New launches:
curl -s -H 'Authorization: Bearer <key>' 'https://app.aurelia.build/api/chains/solana/pulse?view=new&limit=10'
Live data
Open one socket at wss://app.aurelia.build/api/live?apiKey=<key> and subscribe to as many tokens as you need. Every swap is pushed as its block is indexed.
Subscribe to a token's trades:
{"op":"subscribe","id":"t","channel":"trades","chain":"solana","token":"So11111111111111111111111111111111111111112"}
What is specific to Solana
- Holders: complete, one holder per owner, unless the mint has too many token accounts. Then its 20 largest, and the answer says so.
- Wallet activity: read from the chain. Every transaction that names the wallet, with exact balance changes, at most 40 read per request.
- Security: authorities, Token-2022 extensions, metadata mutability and a honeypot signal.
Reference
- Prices API: up to 100 tokens in one request, now or at a past moment.
- Token holders API: the largest holders, with labels and PnL.
- Wallet portfolio API: a wallet's holdings, valued in USD.
- WebSocket API: every live channel.