POST
Create PIX cash-out

Authorizations

Authorization
string
header
required

Authorization: Bearer cl_test_sk_... (sandbox) or Bearer cl_live_sk_... (live). A live key additionally needs production enabled by the workspace owner. Using a live key against the sandbox path revokes it on sight (leak signal); a sandbox key on live is refused and logged, but not revoked.

X-Workspace-Id
string
header
required

The workspace (tenant) UUID. Always required, including on session-authenticated dashboard calls.

Headers

X-Subaccount-Id
string<uuid>

Wallet-as-a-service: act on one of the caller's own sub-accounts (its ledger, parties and wallets) instead of the workspace itself. Only valid on balances/wallets/transactions/statement/crypto/pix/payment-links/rfq routes, only for a workspace-level caller (not a party-scoped key), and only for a sub-account the caller's workspace owns.

Idempotency-Key
string
required

Required. The same key with the same request body replays the stored result; the same key with a different body is 409 idempotency_key_reuse.

Path Parameters

env
enum<string>
required

test is also accepted on the wire as an alias of sandbox; the key prefix must match (cl_test_sk_ for sandbox/test, cl_live_sk_ for live).

Available options:
sandbox,
live

Body

application/json

A session (dashboard) caller must supply payout_account_id — this call only initiates and shows the resolved receiver; confirm with POST /pix/payouts/{id}/confirm. An API-key caller must omit payout_account_id and supply pix_key directly; that single call holds and pays.

amount_minor
required

Integer minor units (BRL scale 2).

Pattern: ^[0-9]{1,16}$
currency
string
default:BRL
pix_key
string

Required unless payout_account_id is given (session callers) or the workspace is pinned to a settlement key.

payout_account_id
string<uuid>

Session callers only; selects a saved PayoutAccount.

party_id
string<uuid>
description
string
receiver_name
string

Checked against the provider-resolved receiver; a mismatch on name is not enforced, only on document.

receiver_document
string

CPF/CNPJ the caller expects to receive; mismatch with the resolved receiver is receiver_document_mismatch.

pix_key_type
string

Used only to match an approval-gate request, not validated server-side here.

approval_id
string<uuid>

Links this payout to a previously approved multisig request.

Response

Idempotency-Key replay.

data
object
required

A payment intent / ledger-facing operation: a PIX cash-in or cash-out, a crypto send, or an RFQ settlement. Exact fields vary by kind.