Change a PIX transaction limit
Changes the amount of ONE existing limit row. The row is addressed by its natural key rather than by an id: accountId, plus periodType (DAILY, NIGHTLY or MONTHLY, case-insensitive) and limitType (TRANSACTION or PERIOD, case-insensitive); transactionType is always PIX. amount is the new cap in centavos and must be greater than zero.
It is update-only. It never creates a row, and no other endpoint does either - the four default rows appear only after POST /v1/transactions first runs the limit check for the account (see GET /v1/limits). A MONTHLY row, which the service never seeds, therefore cannot be changed here.
The refusals are worth knowing before you debug one: an unknown periodType, an unknown limitType, and a well-formed tuple with no matching row ALL answer 422 PIX-0036, carrying the message about a transaction status transition not being permitted, and nothing in the response tells the three apart. A non-positive amount is the one distinct case, 422 PIX-0030 naming the amount. A new cap applies from the next POST /v1/transactions; there is no scheduling and no approval window.
Authorizations
JWT bearer token issued by the identity provider.
Body
The account id (externalId).
"ext-acc-123"
The new limit amount in centavos (> 0).
5000000
eTransactionLimitType name (TRANSACTION/PERIOD).
"PERIOD"
ePeriodType name (DAILY/NIGHTLY/MONTHLY).
"DAILY"
Response
OK
The account id (externalId).
"ext-acc-123"
The limit amount in centavos.
5000000
The limit row id.
"l1f9c0a2-..."
eTransactionLimitType name.
"PERIOD"
ePeriodType name.
"DAILY"
eTransactionType name.
"PIX"

