curl https://api.liddie.io/api/v1/whitelist \
-H "Cookie: <dashboard session cookies>"
// Dashboard-session auth: send the session JWT as a Bearer token
const res = await fetch('https://api.liddie.io/api/v1/whitelist', {
headers: { Authorization: `Bearer ${dashboardJwt}` },
})
const { ok, data } = await res.json()
{"ok":true,"data":{"wallets":[],"ips":[]}}
Whitelist
Get the withdrawal whitelist
List the crypto wallet addresses and IPs on your Liddie whitelist. Wallets gate where withdrawals may go; IPs gate where withdrawals may be requested from.
GET
/
api
/
v1
/
whitelist
curl https://api.liddie.io/api/v1/whitelist \
-H "Cookie: <dashboard session cookies>"
// Dashboard-session auth: send the session JWT as a Bearer token
const res = await fetch('https://api.liddie.io/api/v1/whitelist', {
headers: { Authorization: `Bearer ${dashboardJwt}` },
})
const { ok, data } = await res.json()
{"ok":true,"data":{"wallets":[],"ips":[]}}
Returns your withdrawal whitelist: approved wallet addresses (where funds may go) and approved IP entries (where a withdrawal may be requested from).
Outbound money always goes to a whitelisted address — withdrawals, auto-withdrawal rules and mass payouts all check this list server-side — so this list is the gate for all egress (outbound money movement).
The example shows a merchant with no whitelist entries yet.
curl https://api.liddie.io/api/v1/whitelist \
-H "Cookie: <dashboard session cookies>"
// Dashboard-session auth: send the session JWT as a Bearer token
const res = await fetch('https://api.liddie.io/api/v1/whitelist', {
headers: { Authorization: `Bearer ${dashboardJwt}` },
})
const { ok, data } = await res.json()
{"ok":true,"data":{"wallets":[],"ips":[]}}
Authorization
Dashboard-only (JWT session). Roles:merchant_admin / merchant_member / super_admin, with team permission whitelist:view.
No API-key scope reaches this endpoint — calling it with an API key fails with 401 {"error":"Invalid or expired token"} (the key is not a JWT).
This endpoint takes no parameters — the whitelist scope is inferred from your dashboard session.
Response
| Field | Description |
|---|---|
ok | Success discriminator — true when the request succeeded. |
data.wallets | Whitelisted wallet address entries. Empty array when none have been added. |
data.ips | Whitelisted IP entries allowed to request withdrawals. Empty array when none have been added — which means no IP restriction. |
Errors
| Status | Body | Why |
|---|---|---|
| 401 | {"error":"Invalid or expired token"} | Called with an API key (or an expired session) — this endpoint is dashboard-JWT only. |
See also
- Add wallet address: add an egress destination to the whitelist (MFA-gated).
Both halves are enforced, on opposite conventions. Wallet entries decide where funds may go: a withdrawal destination must match a whitelisted
(currency, address, tag) triple, and an empty wallet list means no withdrawals at all. IP entries decide from where a withdrawal may be requested, and an empty IP list means no restriction — it only becomes an allowlist once you add the first entry. See Add IP address.- Remove whitelist entry: delete a wallet or IP entry by its id.
- Request a withdrawal: withdrawals only pay out to addresses on this list.