Confirm PIX key OTP
Second step of registering an email or phone PIX key. Send the
challengeId returned by POST .../pix/keys (202 pending_verification) together with the 6-digit code the holder
received. On success the key is registered at the partner and the
response is the same 201 as a direct registration. Wrong code
returns code_invalid; after too many attempts the challenge is
locked (challenge_locked) and a new registration is required.
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Path parameters
Headers
Optional client-generated idempotency token (recommended for safe retries).
Unix seconds. Required on the signed host; tolerance is 300s either way (403 request_timestamp_skew).
Lowercase hex SHA-256 of the body. An empty body hashes the empty string, so the header is always present. Mismatch returns 400 body_hash_mismatch.
Detached JWS (<protected>..<signature>, ES256 or PS256) over METHOD\nPATH?QUERY\nTIMESTAMP\nIDEMPOTENCY_KEY_OR_EMPTY\nX_CONTENT_SHA256.
Request
6-digit OTP. Never logged.