Skip to main content
POST
Recreate boleto

Authorizations

Authorization
string
header
required

Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.

Headers

Trio-Version
enum<string>
required

Version of the v2 contract the client is written against. Each breaking change publishes a new version.

Available options:
2026-10-19.v2
Trio-Target-Org-Id
string<uuid>

ID of another org to act on instead of the API key's own org. The key's org must have been granted access to it, and the request is refused with 403 FORBIDDEN otherwise. When that access or the API key is read-only, only GET and HEAD requests may carry it. When the target org requires mTLS, so does the request. Leave it out to act on the key's own org.

Path Parameters

id
string<uuid>
required

Boleto Id Unique identifier

Body

application/json

The new amount and due date

Body params to recreate a boleto: it is cancelled and a new boleto is created with the same fields, the new amount and the new due date (or the current one when due_detail is omitted).

amount
integer
required

New amount in cents

Required range: x >= 1
due_detail
object | null

Response

Recreated

Response for boleto

data
V2 Boleto_Response_Params · object

A boleto

Example: