Skip to main content
PATCH

Authorizations

Authorization
string
header
required

JWT bearer token issued by the identity provider.

Headers

X-Account-Id
string<uuid>
required

Non-zero UUID of the payer account selected by the calling PSP. The PSP must authorize its end user for that account before calling this API. A resource outside the selected account returns 404; a read with no records returns an empty page. See the API overview for the complete trust boundary.

Pattern: ^[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-[0-9A-Fa-f]{4}-[0-9A-Fa-f]{4}-[0-9A-Fa-f]{12}$
X-Idempotency
string
required

REQUIRED. Client-supplied replay key, at most 64 bytes. A request without it is refused with PIX-0030 @ 400 before the handler runs. Replaying the same key with a divergent method, URL or body is PIX-0031 @ 412. X-Account-Id is part of the compared request too, so replaying one account's key under another account is divergent rather than a replay.

Required string length: 1 - 64

Path Parameters

authorization_id
string
required

Internal identifier of the mandate whose parameters are being changed. A request or mandate that exists under a DIFFERENT account than X-Account-Id names is answered 404, not 403: the lookup carries the account as a predicate, so this end never learns that a resource exists elsewhere and cannot confirm it.

Example:

"01a044a8-f3bd-7488-a0dc-e8d4be4802be"

Body

application/merge-patch+json

The merge-patch document. Every property is optional, and null is meaningful on all three.

creditLineEnabled
boolean | null

Whether a pre-approved credit line may be drawn on when the balance is short at settlement (Guia v1.2 §6.3). Null restores the normative default, which is true.

Example:

false

maximumAmount
object | null

Ceiling per payment under this authorization. Null removes the ceiling, which is its normative default (Guia v1.2 §6). Checked at scheduling, never at settlement, and never shared with the receiving user or their PSP (§6.1).

Example:
schedulingNotificationsEnabled
boolean | null

Governs ONLY the notice of a successful scheduling (Guia v1.2 §6.2). Null restores the normative default, which is true — a reset is NOT an opt-out.

Example:

false

Response

Parameters updated. The body carries the three parameters as they now stand.

authorizedAt
string<date-time>
required
Example:

"2026-08-27T19:18:38Z"

createdAt
string<date-time>
required
Example:

"2026-08-27T19:18:38Z"

id
string
required
Example:

"01a044a8-f3bd-7488-a0dc-e8d4be4802be"

journey
string
required
Example:

"JOURNEY_1"

parameters
object
required
recurrenceId
string
required
Example:

"RR12345678202608276bca619e690"

status
string
required
Example:

"APPROVED"

updatedAt
string<date-time>
required
Example:

"2026-08-27T19:20:00Z"