Apply a judicial block on a PIX key
Mirrors a Banco Central ofício onto this deployment’s own key book (DICT 8.4 section 1.1): the key stops resolving on every internal query, which answers the block indication with none of the key’s permitted data, and update, delete and claim all refuse it. The ofício reaches the participant on paper, so without this route the rail learns of the block only when a later call to BACEN happens to come back EntryBlocked — and keeps resolving the key with full owner and account data until then. One identified operator, no second approval: mirroring a court order is an obligation and not a judgement call. The ofício reference is mandatory and the act is audited under the caller’s identity before and after the effect. Idempotent: a key already blocked answers 200 with alreadyApplied. A key whose current state cannot hold the block (never confirmed by BACEN, or already deregistered) is refused with 422.
Authorizations
JWT bearer token issued by the identity provider.
Body
PIX key the ofício names, in its canonical format for the key type. At most 77 characters, the ceiling BACEN publishes on a DICT key.
1 - 77"12345678901"
Reference of the Banco Central ofício ordering (or revoking) the block — process number, document id, whatever the order carries. Recorded in the audit trail under the caller's identity and never emitted on the event topic. Operator prose only: never a tax id, a Pix key, an account or a holder name.
8 - 384Response
OK
The key, as supplied.
"12345678901"
The key's status after this call.
ACTIVE, INACTIVE, PENDING_CLAIM, PENDING_BACEN_SYNC, BLOCKED "BLOCKED"
True when the key was already on the requested side of the block and nothing was written. 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.

