Withdrawals - IMBA API

Scope: withdraw.

Create withdrawal

POST https://api.imbawallet.com/partner/withdrawals
Authorization: Bearer <access_token>
Content-Type: application/json

{
  "currency": "USDT",
  "network": "TRON",
  "amount": "100.50",
  "to_address": "TExamplePartnerWithdrawAddr22222",
  "ext_id": "withdraw-20260710-001"
}

amount is the sum sent to to_address (excluding IMBA fee). Available balance must cover amount + fee.

Response `202`

{
  "withdrawal_id": "019d0123-bf52-74b5-b78a-76c49333e82d",
  "ext_id": "withdraw-20260710-001",
  "currency": "USDT",
  "network": "TRON",
  "amount": "100.50",
  "fee": "1.00",
  "fee_currency": "USDT",
  "to_address": "TExamplePartnerWithdrawAddr22222",
  "status": "pending",
  "created_at": "2026-07-10T09:20:00.000Z"
}

Status lifecycle

pending → processing → completed | failed | cancelled

Track with:

Webhook withdrawal.status_changed
GET /partner/documents/{ext_id}

Errors

Code	Typical HTTP
`invalid_address`	400 / 422
`unsupported_asset`	400 / 422
`invalid_amount`	400 / 422
`insufficient_balance`	409
`withdrawals_disabled`	403 / 503
`withdraw_limit_exceeded`	409
`ext_id_conflict`	409

Daily withdraw caps may apply per tenant (withdraw_limit_exceeded). See Rate limits. There is no partner cancel-withdrawal endpoint. Terminal states include failed and cancelled (provider / ops). IMBA withdraw fee is on the order of 1 USDT (live fee on the create response).