API Reference
Usage examples
GET /api/wallet/tracker?wallet=G6fUXjMKPJzCY1rveAE6Qm7wy5U3vZgKDJmN1VPAdiZC&period=1d&chain=SOL&api_key=YOUR_KEYGET /api/wallet/tracker?wallet=0x7a2363a401b2340c7941dd2eeff0196a5078d2e6&period=7d&chain=BNB&api_key=YOUR_KEYGET /api/wallet/tracker?wallet=0xa83b73f5644cde337b61da79589f10ea15548811&period=30d&chain=BASE&api_key=YOUR_KEYIntegration guide
Chain
Category
Endpoint
Query parameters
api_keystringRequiredExample:
Your valid API key
AjSk9daaZh4vte6KxJc1FZVJMfO8dwdWlKj8H9walletstringRequiredExample:
Wallet address to look up.
- Solana: base58 encoded public key (~44 characters)
- BNB / Base: EVM address starting with
0x
G6fUXjMKPJzCY1rveAE6Qm7wy5U3vZgKDJmN1VPAdiZCperiodstring · enumOptionalDefault:
Time period for stats and trade history. Defaults to 1d.
1dExample: 1dPossible values: chainstring · enumOptionalExample:
Force a specific chain for this wallet lookup.
Recommended when linking from a leaderboard — BNB and Base both use
0x addresses, so a wallet can exist on both chains simultaneously.
If omitted, the chain is detected automatically.
BNBPossible values: Responses
200
Wallet found — returns full trading profile
application/json
400
Missing or invalid parameter
application/json
403
Invalid or exhausted API key
application/json
404
Wallet not found. This means the wallet is not tracked by CabalSpy. Only wallets that appear in the leaderboard endpoints can be queried. Arbitrary wallet addresses will always return 404.
application/json
500
Internal server error
application/json
get
/api/wallet/trackerLast updated