Account setup
From sign-up to a strategy your bot can trade.
Everything in this page happens in the Wellat web dashboard. Nothing here is done through the API.
1. Sign up and complete KYC
Create a Wellat account and complete identity verification. The Bot API is not available until KYC is approved.
Screenshot: KYC status on the profile page.
2. Switch to the Trader profile
Wellat accounts have two profiles: Copier (follows strategies) and Trader (manages strategies). Bot strategies belong to the Trader profile.
Open the profile switch at the top-right corner of the dashboard and select Trader. The dashboard changes: you now see Create strategy and API keys.
Screenshot: the profile switch, top right.
3. Create an API key and secret
- Go to API keys (visible only on the Trader profile).
- Click Create API key.
- If you have not enabled two-factor authentication yet, you are asked to set it up now. API keys cannot be created or revoked without 2FA.
- Enter your 2FA code and give the key a label, for example
grid-bot-btc.
You receive two values:
| Value | Format | Shown |
|---|---|---|
| API key | wlt_bot_ followed by 64 hex characters | Always visible in the key list |
| API secret | 64 hex characters | Once, at creation |
The secret is never stored on Wellat's side: it is derived when you create the key and recomputed when your requests are verified. If you lose it, revoke the key and create a new one.
Screenshot: the API key creation dialog with the secret shown.
Keep the secret out of source control. Put it in an environment variable or a secrets manager. Anyone holding the key and secret can trade your strategy.
4. Create a strategy and bind the key
Click Create strategy on the Trader dashboard and choose the type:
| Type | Markets | API family your bot uses |
|---|---|---|
| Spot | Spot pairs | /api/v3 |
| Futures | USDⓈ-M perpetuals | /fapi/v1, /fapi/v2, /fapi/v3 |
In the creation form, select the API key that will manage this strategy. From then on every request signed with that key is executed against this strategy. A key manages one strategy at a time; create another key for another strategy.
Screenshot: the strategy creation form with the API key selector.
The strategy runs in demo with a virtual balance; copiers who join mirror its orders on their real accounts. Your bot never deposits.
5. Check the binding
Your bot can confirm the key is live with one signed read:
# Spot strategy
GET /api/v3/account
# Futures strategy
GET /fapi/v3/account
A 200 with balances means the key, secret, strategy and family all line up. The two errors you can hit at this point:
| Response | Meaning |
|---|---|
401 { "code": -2015 } | Wrong secret, revoked key, or missing X-MBX-APIKEY. |
400 { "code": -2010, "msg": "This key is bound to a SPOT strategy; use /api/v3" } | You called the other family. |
Revoking a key
Revoke a key from the API keys page (2FA required). Requests signed with it fail with -2015 immediately. The strategy keeps its history; bind a new key to keep trading it.
Updated 10 days ago