Change a PIX key entry
Re-points an existing PIX key to a new transactional account and/or a new owner name inside the SAME participant (§8.2.02 Alterar Chave de Endereçamento). entryId is the key VALUE, URL-encoded, and it never changes - no operation in this API edits a key’s value.
Only the destination travels in the body: newBranch, newAccountType, newAccount, accountOpeningDate, newName and newTradeName, all optional per the spec. The owner identity (ISPB, CPF/CNPJ, person type) is derived server-side from accountId and is never read from the payload. reason is required and is DICT’s motivo: 0=Customer Request, 2=Branch Transfer, 6=Reconciliation, 8=Receita Federal Validation; an EVP (RANDOM) key must not use 0.
It is a pure control-plane write: the plugin does NOT touch its own key row, so GET /v1/entries reflects the change only through its DICT source and a local row keeps the old coordinates until then. DICT may open a possession or portability claim as a consequence of the change; when it does, the response carries claimOpenedAt. Failures are DICT’s, translated into the PIX-1xxx family - an unknown key is 404 PIX-1011.
Authorizations
JWT bearer token issued by the identity provider.
Path Parameters
The PIX key value (URL-encoded).
"foo@bar.com"
Body
The CRM account id of the key owner (resolves the server-side ISPB).
"acc-123"
Change reason (0=Customer Request,2=Branch Transfer,6=Reconciliation,8=Receita Federal Validation). EVP keys must not use 0.
2
The new account's opening timestamp (RFC3339).
"2020-01-10T11:30:17.001Z"
The new account number to associate with the key.
"0007654321"
The new account type (0=Checking,1=Salary,2=Savings,3=Payment,4=PI).
0
The new branch number to associate with the key.
"0001"
The new owner full name / legal name.
"Empresa Nova"
The new owner trade name (sent only for a corporate owner).
"Fantasia Nova"
Response
OK
The PIX key (unchanged).
"foo@bar.com"
When a possession/portability claim was opened by the change (RFC3339), if any.
"2026-01-03T00:00:00Z"
When the key was created (RFC3339).
"2026-01-01T00:00:00Z"
When ownership of the key began (RFC3339).
"2026-01-02T00:00:00Z"

