Account settings & KOLs
Read and change your trading settings and the wallets you track (KOLs) from code, and what stays in the app.
Two account-level settings pages are on the API: the temporary-wallet sell settings and the KOL tracker. Reads need read, writes trade.
Trading settings#
GET /settings/trading is the Settings → Trading page:
{
"sellThroughTemporaryWallet": true,
"temporarySellMode": "all",
"temporarySellManual": { "simple": true, "uniqueWallet": true, "percentage": true, "sellAll": true, "sellAllExceptDev": true, "sellDev": true, "tradePanel": true },
"temporarySellTasks": true,
"temporarySellTaskTypes": { "…": true }
}PATCH /settings/trading takes either the one switch — { "sellThroughTemporaryWallet": false } — or the full custom shape (temporarySellMode of off, all or custom with temporarySellManual, temporarySellTasks and optionally temporarySellTaskTypes). The answer is the settings after the change. The setting applies to every sell you make afterwards, from the app, the API and tasks alike.
Tracked wallets (KOLs)#
The addresses the terminal marks as KOLs are yours to edit:
| Method & path | Does |
|---|---|
GET /kols | Your tracked addresses (paged) |
POST /kols | Track one: { "address": "…", "name": "…", "emoji": "🐳" } → 201 { "kol": { "id", "address", "name", "emoji", "createdAt" } } |
PATCH /kols/:address | Change name or emoji (null clears) |
DELETE /kols/:address | Stop tracking it → { "removed": "…" } |
An address that is not on your list is a 404; tracking one twice is a 409 with code: "conflict".
What stays in the app#
- API keys. Creating, editing and revoking keys is only possible signed in, in the API hub. A key that could mint keys would be a way around every limit you put on it.
- Wallet private keys never leave the platform through the API: there is no export route.
- Sign-in, password and profile, the marketplace, referrals, subscription and support tickets are app-only.