1. API Endpoints
Pix2DePix API
  • ⚡ Quickstart
  • Guides
    • 🔑 Authentication
    • 🔄 Possible Statuses
    • 🔀 Synchronous requests & safe retries
    • ⚠️ Errors & the response envelope
    • 🧯 Troubleshooting
    • ✅ Best Practices
    • 🚀 Features
      • ⏱️ QR Delay
    • 🛡️ Security & Limits
      • 🚦 API Limits
      • 🧱 Firewall
      • 🪲 Bug Bounty
    • 🧭 Networks
      • 🌐 Networks and payout addresses
      • 💧 Liquid network guide
      • 📚 Arkade network guide
      • ✨ Spark network guide
  • API Endpoints
    • Ping
      GET
    • Deposit (PIX ➔ DePix)
      POST
    • Deposit Status
      GET
    • Deposits
      GET
    • User Info
      GET
    • Withdraw
      POST
    • Withdraw Status
      GET
  • Webhooks
    • 🪝 Webhooks
    • Deposit Webhook
    • Withdraw Webhook
    • MED Webhook
  • Reference
    • 📖 Glossary
    • 📝 Changelog
  • Schemas
    • JWTClaims
    • ErrorObj
    • PingObj
    • ErrorResponse
    • DepositObj
    • PingResponse
    • DepositResponse
    • DepositStatusObj
    • DepositStatusResponse
    • DepositWebhookBody
    • DepositsResponse
    • DepositStatus
    • UserInfoResponse
    • WithdrawStatusResponse
    • WithdrawStatusObj
    • WithdrawResponse
    • WithdrawObj
    • WithdrawStatus
    • WithdrawWebhookBody
    • MEDWebhookBody
    • RejectionReasons
  1. API Endpoints

Withdraw

POST
/withdraw
Creates a withdrawal: you fund a blockchain address that this endpoint returns, and we pay the amount out to a Pix key with the fees already deducted.

How to use this API correctly#

Use EXACTLY ONE of the following amount parameters:
Only depositAmountInCents if you want to specify the amount you want to send in DePix.
OR only payoutAmountInCents if you want to specify the amount you want to receive in Pix (Reais).
By sending one of the two parameters, the other will be automatically calculated according to our fees and will be returned in the response.
It is not possible to use both amount parameters in the same request, and you cannot leave both empty.
The amount paid out to the Pix key is bounded per withdrawal: from R$ 2,00 to 6.000,00, after the fee. These are the values of the default partner profile; an account on another profile has its own, and the refusal below states them.
With payoutAmountInCents the bound applies to the value you send. With depositAmountInCents it applies to what remains once the fee is deducted, so a depositAmountInCents of 200 pays out R$ 1,00 and is refused. The bound is per operation, never a daily total. Outside it the request is rejected with Withdrawal amount (<payout> cents) is outside the allowed per-transaction range: min <min> cents, max <max> cents. On a profile without a maximum the refusal reads Withdrawal amount (<payout> cents) is below the allowed per-transaction minimum of <min> cents.
Withdrawals are also capped per day for each recipient tax number. When a withdrawal is refused for it, the message states the day's volume and the cap in cents: Daily withdrawal limit exceeded for pix key '<pixKey>'. Daily volume in cents: <volume>. Withdrawal limit in cents: <limit>.
On the default partner profile the withdrawal fee is 1% with a floor of R$ 1,00. On small withdrawals the percentage rate is not what you pay: whichever is larger between the rate and the floor is deducted. The rate in force on your account is answered by /help on Telegram; the floor is not shown there, so ask support for it if your account is not on the default profile.
All withdrawal requests must include the beneficiary identification.
You must send at least one of the following identification parameters:
taxNumber: the CPF or CNPJ of the Pix key owner.
euid: the Eulen User Identification.
The request will be rejected if neither taxNumber nor euid is provided.
If both taxNumber and euid are provided, the informed taxNumber must match the corresponding euid. If they do not match, the request will be rejected.
The Pix key must belong to the informed taxNumber.
If the Pix key ownership does not match the provided identification, the withdrawal may be automatically rejected by the banking system.
The DePix you send must match what the withdrawal expects, within 5%.
Within 5%, in either direction, the withdrawal still goes through and the payout is recalculated from the amount that actually arrived. What is paid in Pix is then no longer the payoutAmountInCents returned when the withdrawal was created; read GET /api/withdraw-status for the amount actually paid.
Above 5%, the deposit is ignored and the withdrawal is left untouched. You are notified on Telegram, and the notification names the withdrawal id and the transaction id.
A recalculated payout is checked again against the R$ 2,00 minimum. Falling below it also ignores the deposit, which is why a deposit slightly under the expected amount can be dropped: after fees there is less than the minimum left.
An ignored deposit is returned automatically, in full and with no fee withheld, when the withdrawal has a refund address: the refundAddress declared on it or, without one, your partner default refund address (see below).
Send refundAddress if you want the DePix back when a payout cannot be completed.
refundAddress is an optional Liquid address, and it is where your DePix is returned if this withdrawal cannot go through.
Declare it here, on the request, because it cannot be recovered afterwards. Liquid is a confidential chain and does not reveal who sent a transaction, so there is no way for us to work out where the DePix came from.
When a withdrawal declares no refundAddress, the refund goes to your partner default refund address. An allowlisted member of your Telegram group sets it with /setrefundaddress <liquid-address> and removes it with /setrefundaddress none. The default is read when the refund happens, so it also covers withdrawals created before it was set. It returns the DePix to you, not to your end customer: to refund a customer directly, declare refundAddress on that withdrawal. Without either address, the funds stay put until our team reaches you to ask where to send them.
Any Liquid address you control works, including the one you send the DePix from.
Maximum 128 characters, no spaces. The address is checked when the request is made; an invalid one is rejected with invalid 'refundAddress' param, and a non-string value with 'refundAddress' should be a string.
The recorded value comes back on GET /api/withdraw-status, so you can confirm what was stored.
What returns is DePix on the Liquid Network. It is never Reais, and it never reaches the beneficiary's Pix key. The withdrawal then reports the refunded status, listed on Possible Statuses.
A 1 DePix fee is withheld when the payout could not be completed because of the request itself: the Pix key does not belong to the informed taxNumber, or the Pix key is invalid or was rejected at payout. It is also withheld when the recipient was past the daily withdrawal limit. The fee is reported in refund.feeInCents on GET /api/withdraw-status, next to the amount returned in refund.netAmountInCents: what arrives at refundAddress is the DePix that actually arrived for this withdrawal, minus it.
No fee is withheld when the failure was not on the request: our side or the banking processor broke, or the DePix that arrived did not match what the withdrawal expected. Those return in full.
Do not send the DePix after the withdrawal has expired.
DePix that arrives late is not paid out. What happens to it depends on the refund address: with a refundAddress declared on the request, or else your partner default refund address, the DePix can be returned there; without either, the funds stay put until our team reaches you to ask where to send them.

Request

Authorization
JWT Bearer
Add the parameter
Authorization
to Headers
Example:
Authorization: ********************
or
Body Params application/jsonRequired

Example
{
    "pixKey": "example@example.com",
    "depositAmountInCents": 124647,
    "payoutAmountInCents": 123400,
    "taxNumber": "12345678909",
    "euid": "EU011234567890128"
}

Request Code Samples

Shell
JavaScript
Java
Swift
Go
PHP
Python
HTTP
C
C#
Objective-C
Ruby
OCaml
Dart
R
Request Request Example
Shell
JavaScript
Java
Swift
curl --location 'https://depix.eulen.app/api/withdraw' \
--header 'Content-Type: application/json' \
--data-raw '{
    "pixKey": "example@example.com",
    "depositAmountInCents": 124647,
    "payoutAmountInCents": 123400,
    "taxNumber": "12345678909",
    "euid": "EU011234567890128"
}'

Responses

🟢200Success
application/json
Headers

Bodyapplication/json

Example
{
    "response": {
        "withdrawalId": "019b76daa800700000000000000000a1",
        "depositAddress": "lq1qqtkuz7nwp3cymteg0px5pcltrm26uvsak32t04fawfsacafutjg22fhvc8xhj0ue96cevuatnmt757rf4z2r5cwntsemgngcr",
        "depositAmountInCents": 124647,
        "payoutAmountInCents": 123400
    },
    "async": false
}
🟠400Malformed request
🟠401Not authenticated
🟠403Not allowed
🟠413Body too large
🟠422Compliance denial
🟠429Rate limited
🔴500Internal error
🔴502Bad upstream reply
🔴503Unavailable
🔴520Rejection
Modified at 2026-11-17 01:51:35
Previous
User Info
Next
Withdraw Status
Built with