Release an end user's DICT key queries
Releases a block once the operator has established that the behaviour was justified, or that the suspicion no longer holds: the end user’s key queries are served again, subject to the section 13.1 buckets that never stopped applying. Same posture as placing it — one identified operator, mandatory justification, audited under their identity. Idempotent: an end user carrying no block answers 200 with alreadyApplied.
Autorizaciones
JWT bearer token issued by the identity provider.
Cuerpo
Why this end user is being blocked or released — the verified suspicion section 13.2.3 conditions the act on, in the operator's own words. Recorded in the audit trail under the caller's identity. Operator prose only: never a tax id, a Pix key, an account or a holder name.
8 - 384The end user's CPF or CNPJ, digits only — the same identifier their key queries carry in PI-PayerId. Hashed immediately and never stored, logged or returned. Supply this OR payerIdHash, not both.
^([0-9]{11}|[0-9]{14})$"12345678901"
Keyed digest of the end user's CPF/CNPJ, as the monitor read reports it. Supply this OR payerId, not both.
^[0-9a-f]{64}$"9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08"
Respuesta
OK
Whether this end user's DICT key queries are blocked after the call.
true
Keyed digest of the end user this call acted on.
"9f86d081884c7d659a2feaa0c55ad015a3bf4f1b2b0b822cd15d6c15b0f00a08"
True when the end user was already on the requested side and nothing changed. The call is a success either way and is still audited under the caller's identity, so re-sending a request whose response was lost is safe.

