Skip to main content
POST
Initiate fiat withdrawal
Initiates a fiat withdrawal to an approved bank account. The target account must already exist in the organization’s approved fiat withdrawal accounts — retrieve its ID via List fiat withdrawal accounts. Use this endpoint to:
  • Send USD, EUR, GBP, AED, AUD, MXN, BRL, PHP, ARS, or COP to an approved bank account
  • Initiate fiat payouts from the organization’s balance
  • Record a withdrawal that can later be tracked by ID
Idempotency required. This POST requires an Idempotency-Key header. Keys are cached for 7 days. Reusing the same key with the same body returns the cached response; reusing it with different parameters returns a 422 error.
FEDWIRE payment details. Once a USD FEDWIRE withdrawal settles, the bank-side identifiers (IMAD outbound, OMAD inbound) are surfaced on the withdrawal record under paymentDetails.FEDWIRE. Poll GET /v2/brokerage/{orgId}/withdrawal/{withdrawalId} after submission to pick them up — they may not appear on the initial response.

Errors

See the full v2 error reference for retry semantics and idempotency-specific codes.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

Idempotency-Key
string<uuid>
required

Unique key to ensure idempotent requests. UUID v4 recommended. Valid for 7 days.

Example:

"123e4567-e89b-12d3-a456-426614174000"

Path Parameters

orgId
string
required

Body

application/json
amount
number
required
Example:

10

currency
enum<string>
required
Available options:
USD,
AED,
GBP,
EUR,
AUD,
MXN,
BRL,
PHP,
ARS,
COP
Example:

"USD"

withdrawalAddressId
string<uuid>
required
Example:

"123e4567-e89b-12d3-a456-426614174001"

Response

success

status
enum<string>
Available options:
success,
error
Example:

"success"

data
object
message
string
Example:

"Data fetched successfully"