curl -X POST https://api.liddie.io/api/v1/whitelist/send-email-code \
-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/send-email-code', {
method: 'POST',
headers: { Authorization: `Bearer ${dashboardJwt}` },
})
const body = await res.json()
Whitelist
Send whitelist email code
Send a single-use email code to authorize Liddie whitelist changes — adding wallets or IPs, or removing entries — with the emailCode MFA factor.
POST
/
api
/
v1
/
whitelist
/
send-email-code
curl -X POST https://api.liddie.io/api/v1/whitelist/send-email-code \
-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/send-email-code', {
method: 'POST',
headers: { Authorization: `Bearer ${dashboardJwt}` },
})
const body = await res.json()
Emails a single-use MFA code to the account’s email address. Pass the received code as the email-code verification factor in the whitelist mutation endpoints: Add wallet address, Add IP address, Remove whitelist entry.
This endpoint takes no parameters — the email address is inferred from your dashboard session.
curl -X POST https://api.liddie.io/api/v1/whitelist/send-email-code \
-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/send-email-code', {
method: 'POST',
headers: { Authorization: `Bearer ${dashboardJwt}` },
})
const body = await res.json()
Authorization
Dashboard-only (JWT session). Roles:merchant_admin / merchant_member / super_admin, with team permission whitelist:manage. Rate limit: 3 per 15 minutes.
Calling with an API key fails with 401 {"error":"Invalid or expired token"} — the key is not a JWT.
The code is single-use and this endpoint is rate limited to 3 requests per 15 minutes — request a code only when you are ready to submit the whitelist change, then pass it as the email-code verification factor in the follow-up mutation.
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: the mutation that consumes this code as its MFA factor.
- Add IP address: also accepts the emailed code as its MFA factor.
- Remove whitelist entry: also accepts the emailed code as its MFA factor.