Issue a bank slip | CorpX API

curl -X POST https://tenant.api.corpx.com/v1/accounts/accountId/bank-slips \
     -H "X-Tenant-Id: X-Tenant-Id" \
     -H "Authorization: Bearer <token>" \
     -H "Content-Type: application/json" \
     -d '{
  "dueDate": "2026-02-20",
  "amount": {
    "nominal": 150.75,
    "currency": "BRL"
  },
  "payer": {
    "name": "MARIA DA SILVA",
    "personType": "person",
    "taxNumber": "12345678000190",
    "email": "maria.silva@example.com",
    "addressStreet": "string",
    "addressNumber": "string",
    "addressComplement": "string",
    "addressDistrict": "string",
    "addressCity": "string",
    "addressState": "string",
    "addressZipCode": "203.0.113.10/32"
  },
  "identifier": "order-12345",
  "issueDate": "2026-02-20",
  "expirationPolicy": {
    "allowPaymentAfterDueDate": true,
    "paymentLimitDate": "2026-02-20",
    "blockPaymentAfterLimit": true,
    "decursoGraceDays": 1
  }
}'

Issues a boleto for this account. Scope bank_slip.manage. The feature bank_slip_issuance starts disabled for every tenant, including tenants created after this release. While it is off every bank-slip route returns 403 feature_disabled.

First issuance of an account. If the holder is not yet a beneficiary (or the relationship is closed), this call registers the holder and returns 202 with errorCode: bank_slip_beneficiary_pending and Retry-After: 300. Nothing was issued. Repeat the same body in a few minutes. This happens only on the first issuance of each account.

When the beneficiary is already eligible, the response is 202 with the slip (bankSlipId, barcode, digitableLine). Registration at the central base is still asynchronous: subscribe to bank_slip.registered and bank_slip.registration_failed. Repeating the same identifier returns 200 with the live slip.

There is no write-off of an open slip. DELETE returns 501.

Issues a boleto for this account. Scope `bank_slip.manage`. The feature `bank_slip_issuance` starts **disabled for every tenant**, including tenants created after this release. While it is off every bank-slip route returns **403** `feature_disabled`. **First issuance of an account.** If the holder is not yet a beneficiary (or the relationship is closed), this call registers the holder and returns **202** with `errorCode: bank_slip_beneficiary_pending` and `Retry-After: 300`. Nothing was issued. Repeat the same body in a few minutes. This happens only on the first issuance of each account. When the beneficiary is already eligible, the response is **202** with the slip (`bankSlipId`, `barcode`, `digitableLine`). Registration at the central base is still asynchronous: subscribe to `bank_slip.registered` and `bank_slip.registration_failed`. Repeating the same `identifier` returns **200** with the live slip. There is no write-off of an open slip. `DELETE` returns **501**.

Authentication

AuthorizationBearer

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

Path parameters

accountIdstringRequired

Account identifier.

Request

This endpoint expects an object.

dueDatedateRequired

amountobjectRequired

payerobjectRequired

identifierstringOptional

Idempotency key for this account. Falls back to the Idempotency-Key header.

issueDatedateOptional

expirationPolicyobjectOptional

Response

This identifier was already issued. Body is the live slip.

Errors

400

Bad Request Error

403

Forbidden Error

409

Conflict Error

422

Unprocessable Entity Error

502

Bad Gateway Error