Update a Pix key entry
Updates an existing Pix entry (RFC 7386 JSON Merge Patch). Only account information, name, and trade name can be changed. A branch or account number change resolves the new account in the CRM before BACEN is called: no CRM account refuses the update with PIX-0116 (or PIX-0140 when the CRM is unavailable) and BACEN is not called. Moving the key onto a salary account (SLRY), by stating that account type or by a branch or account number change to an account the CRM records as SLRY, is refused with 422 PIX-0176 before BACEN is called; a key already on a salary account stays updatable. BACEN’s refusals come back as PIX-0120 (the directory does not hold the key), PIX-0100 (it refused the change) and PIX-0106 (the key is not active).
Authorizations
JWT bearer token issued by the identity provider.
Headers
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.
1 - 64Account ID (UUID format)
"019606a1-3b4c-7d8e-9f01-234567890abc"
Reason for the update. For an EVP key it MUST be BRANCH_TRANSFER, RECONCILIATION or RFB_VALIDATION; for every other key type any non-empty value is accepted and recorded as the audit reason.
"USER_REQUESTED"
Path Parameters
Entry ID (UUID format)
"019606c3-5d6e-7f80-1b23-456789012cde"
Body
Response
OK
"2019-11-18T03:00:00Z"
"019606c3-5d6e-7f80-1b23-456789012cde"
"2019-11-18T03:00:00Z"
"2019-11-18T03:00:00Z"
"CPF"
"52998224725"
"019606d4-6e7f-8091-2c34-567890123def"
"a946d533-7f22-42a5-9a9b-e87cd55c0f4d"
"ACTIVE"
"2019-11-18T03:00:00Z"
CRM holder of the key's account. Absent while a key VSync synchronized from the directory waits for its owner's CRM account.
"019606e5-7f80-9102-3d45-678901234ef0"

