Documentation
Manual withdrawal API
Manual withdrawal API
Manual withdrawal API
Checked against PoolNode routes, controllers, DTOs and authentication middleware in Rust revision 655097d2a5 (2026-11-02). Upstream response fields not defined locally are not guaranteed by historical examples; only confirmed request contracts are listed here.
All three endpoints require user JWT and the same JSON body: required sid (u64), and coin (string, explicitly recommended; the controller defaults to BTC).
| API | Purpose |
|---|---|
POST /api/subaccount/withdrawal/can/apply |
Check eligibility |
POST /api/subaccount/withdrawal/submit |
Submit a withdrawal request |
POST /api/subaccount/withdrawal/logs |
Read request history |
{"sid":149,"coin":"BTC"}
Check eligibility before user-confirmed submission. Success does not mean on-chain payment is complete; check history and payout bills afterwards. All use the standard envelope with upstream-defined data; no local fixed response schema or pagination is defined. No amount, address, email code or idempotency-key parameter exists here. After a timeout, inspect history before retrying.