Get your balance
What you can currently send.
Path parameters
orgIdstringRequiredThe opaque organization id issued to you, normally CUID-shaped (for example
cmsx…). It is not anorg_-prefixed alias. Pass it unchanged in every organization-scoped path.
Responses
200Everything a payout can draw on, as one number per currency: what the payment network holds for you (provider) plus the USD stablecoins in your own wallet (wallet, per chain, USDC and USDT at face value). Some routings settle from the network's balance, others price the payout and fund it from your wallet; balances is the sum so you never have to know which. Both sources are read live and cached for up to one minute.
ledger, when present, is our own append-only record of the
network-held balance, per currency, with what is currently
reserved by holds. It is published beside the others and never
summed into them; a difference between provider and ledger is
what GET /balance_transactions exists to explain.
unavailable names any source that could not be read this time.
When it is non-empty the figures are a floor, not the balance:
retry before deciding you cannot fund a payout. In sandbox the
balance is one provider-held USD figure and wallet is always
empty.
Body
currencystringRequiredamountstringRequiredThe USD headline,
providerUSD plus everywalletrow.balancesarray of objectRequiredPer currency, both sources summed. Size payouts against this.
Show 2 properties
currencystringRequiredamountstringRequired
providerarray of objectRequiredPer currency, what the payment network holds for you.
Show 2 properties
currencystringRequiredamountstringRequired
walletarray of objectRequiredPer chain, USD stablecoins in your own wallet. Empty when you hold none, and always empty in sandbox.
Show 3 properties
currencystringRequiredAllowed values:USDCUSDTnetworkstringRequiredChain name.
amountstringRequiredToken units
unavailablearray of stringRequiredSources that failed to read this time. Empty when every figure is live; a non-empty result is not cached, so a retry re-reads.
Allowed values:networkwalletledgerarray of objectRequiredPer currency, from our own append-only record; empty until a movement has been recorded.
Show 4 properties
currencystringRequiredavailablestringRequiredWhat a payout can draw on right now.
heldstringRequiredReserved by holds not yet converted to payouts or released.
totalstringRequiredavailable+held.
Errors
401The key was refused. Nothing ran.
UNAUTHORIZED: missing, invalid or revoked, or a key on a route that does not accept one.KEY_EXPIRED: the key passed the expiry it was issued with. Issue a new one; an expired key cannot be rotated.KEY_IP_NOT_ALLOWED: the key is pinned to source addresses and this request came from another.
403A valid key that may not make this call. Nothing ran.
FORBIDDEN: the key belongs to a different organization.ACCOUNT_BLOCKED: API access for your organization is suspended, and every key is refused until we lift it. Contact support.
429Too many requests. The default ceiling is 100 requests per minute per API credential on a 60-second window. High-volume payout and reconciliation routes declare a 600/minute override, and batch submission a 30/minute ceiling. A separate 2,000/minute per-source-IP abuse ceiling always applies.
Obey
Retry-After; it is in seconds and is authoritative. A 429 means the request was refused before the handler ran. Retry reads normally; retry an idempotent mutation with its sameIdempotency-Key.
Error body · Error
typestringRequiredStable machine-readable code.
detailstringRequiredWhat went wrong, in a sentence. Always a string, so
detail.toLowerCase()is safe.More
This is the field to read on
BAD_REQUESTandPROVIDER_REJECTED, where the type alone does not name the condition.messagestringRequiredThe same text as
detail, kept for integrations written beforedetailexisted. Readdetail.resolutionstringOptionalWhat to do about it, when there is a specific answer. It is not on every error (it is absent on
BAD_REQUEST,NOT_FOUND,PAYOUT_NOT_CANCELABLEandDESTINATION_ACCOUNT_NOT_FOUND), so treat it as optional and fall back todetail.statusintegerRequiredHTTP status, repeated in the body.
statusCodeintegerRequiredThe same value as
status, kept for integrations written beforestatusexisted. Readstatus.requestIdstringRequiredQuote this to support and we can find the exact request. Also sent as the
x-request-idresponse header, which is the only place it appears on a successful response. Success bodies do not carry it. Send your ownx-request-idon the request and we use it, so your trace and ours share one identifier; otherwise we mint one.errorsarray of stringOptionalPresent on VALIDATION_ERROR; names each field that failed.
originalIdempotencyKeystringOptionalOn
DUPLICATE_REQUEST_DETECTEDonly. Send the request again with this to receive the original payout instead of making a second one. Without it there is no way to recover except by risking a double payment.originalPayoutIdstringOptionalOn
DUPLICATE_REQUEST_DETECTEDonly. The payout the first request created.originalBatchIdstringOptionalOn a batch
DUPLICATE_REQUEST_DETECTED. The run the first request created.originalRequestIdstringOptionalOn a
409 PAYOUT_OUTCOME_UNKNOWNreplay. TherequestIdof the call whose outcome is unknown; quote it to support.existingRecipientIdstringOptionalOn
BANK_ACCOUNT_ALREADY_LINKED. The recipient in your organization that already holds this account.existingMethodIdstringOptionalOn
BANK_ACCOUNT_ALREADY_LINKED. The payment method on that recipient.
Branch on type, never on the status or the message. Every error type is listed with what to do about it.
Was this page helpful?