Abandon a claim BACEN never registered
Ends a claim this deployment initiated that BACEN never registered. Such a claim is OPEN with no BACEN id because its createClaim gave up without an answer: every claim verb refuses it with 409, the deadline sweep cannot read it at BACEN, and the claimed key stays taken by it. The claim becomes CANCELLED with resolution NOT_REGISTERED_AT_BACEN, nothing is sent to BACEN, the key is free for a new claim, and dict.claim.cancelled is emitted in the same transaction. It is refused with 409 for a claim that carries a BACEN id (cancel it instead), for a claim that is not OPEN, and while its createClaim is still pending, being sent or waiting for a retry: only an intent that exhausted its retries leaves a claim BACEN will not register. A claim BACEN did register while its answer was lost is not abandonable either: the claimer feed adopts BACEN’s id within its next tick, so check GET /api/v1/dict/discovery-feeds for a held or blocked claimer feed before abandoning. It is refused for a caller with no identifiable principal and for a claimer this deployment does not serve, requires a reason, and writes audit rows naming who, which claim and why. Idempotent — re-sending it for an abandoned claim changes nothing and is still audited.
Authorizations
JWT bearer token issued by the identity provider.
Headers
Required key used to prevent replaying the mutation.
Path Parameters
The claim's own id, as the create call answered it.
Body
Why this claim is being abandoned. It is 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 - 384Response
OK
The claim after the call: CANCELLED with resolution NOT_REGISTERED_AT_BACEN.
States plainly what the abandonment did.
True when the claim had already been abandoned. The call then changed nothing and emitted nothing, and it is still audited under the caller's identity — re-sending the same request is safe.

