Overview
The Bot API is the Discord bot over HTTP. Every command that finds tokens or traders, analyses wallets or looks up addresses has an endpoint that takes the same inputs and returns the same file, for scripts, schedulers and dashboards. Part of the Wallet Database + API plan.
How it differs from the REST API
The REST API answers in the same response. The Bot API works like the bot: the job goes into a queue, you poll until it is done, then you download the file. Three calls instead of one, because these jobs can take from a second to several minutes.
flowchart LR
A[Submit the request] --> B[requestId] --> C[Poll /request/id every 5 s] --> D[url is set] --> E[Download the file]The whole cycle, with the exact shapes, is on The request queue.
Every endpoint and its command
Same base URL, same api_key header as the rest of the API: https://botapi.walletmaster.tools. Every row below is a page of its own.
Find tokens
Endpoint | Discord command | Returns |
|---|---|---|
| /trendingtokens | The most swapped tokens over an interval, .txt |
| /migratedtokens | Tokens that just migrated from a launchpad, .csv or .txt |
| /mcaptokens | Tokens that crossed a market cap in the last days, .csv |
| /athmcap | All-time-high market cap per token, .csv |
Find traders
Endpoint | Discord command | Returns |
|---|---|---|
| /toptraders | The most profitable wallets per token, .zip or one .txt |
| /earlybuyers | The first buyers per token, .zip of .csv |
| /alltraders | Every wallet that traded a token, .zip of .csv |
| /dexwallets | Every wallet active on a venue, .txt |
| /botwallets | Users of a trading bot, .txt |
| /programstats | Custom swap programs in use, .csv |
| /programswaps | Swaps through a program, .csv or .txt |
| /lookuptablestats | Lookup tables in use, .csv |
| /lookuptableswaps | Swaps through a lookup table, .csv or .txt |
Analyze
Endpoint | Discord command | Returns |
|---|---|---|
| /pnlplus | Every metric for every wallet on a list, .csv |
| none, API only | A wallet's first buy of every token it bought, .csv |
| /mcapanalyze | Wallets that first bought a token inside a market cap range, .csv |
| /timestampanalyze | Wallets that first bought a token inside a time window, .csv |
| /buysellfilter | Wallets that traded a token for a SOL amount in a range, .csv |
| /tokensoverlap | Wallets that bought every token on a list inside its window, .txt |
Utility
Endpoint | Discord command | Returns |
|---|---|---|
| /findaddress | Full addresses matching a fragment, .txt |
Your account
Endpoint | What it does |
|---|---|
| The status of one request, and its file when done |
| Your past requests, with their files |
| Your remaining credits |
| Resets the IP address saved for your key |
/metatraders has no endpoint; it is bot-only.
When a request is charged
The same quota as the REST API: 1,000,000,000 credits (1000M) every 30 days, one balance for both. A Bot API request is charged when it is accepted, at the price on Credit costs; a request that is refused at submit costs nothing.
Inputs that are heavy for the bot are heavy for the API. Start with a short interval, a specific token or a small list; a request the server cannot acknowledge within 100 seconds is refused with a timeout, nothing queued, nothing charged.
The API is for personal use. If you want to power a product or a service of your own with Wallet Master data, ask in the Discord server about a custom plan.
Was this page helpful?
Related articles
Built with Helpnode