Re-present a quarantined provider webhook
Returns ONE inbound provider webhook out of quarantine and back into the reconciliation sweep’s claim set, with a full retry budget. Quarantine is the terminal PERMANENTLY_FAILED state: the service modelled the event, could not apply it within its retry budget, and stopped claiming the row. NOTHING IS APPLIED BY THIS CALL. It does not contact the ledger, does not contact the provider and does not change any boleto or payment. It changes one row of the webhook journal so that the ordinary drain picks the delivery up again on its next cycle, through exactly the same processing path every other delivery takes. Watch the drain, not this response, to learn whether the delivery finally applied. It is safe to retry: a row that is no longer in quarantine — because a previous call already released it, or because it never was — is refused with 409 PBP-0007 rather than released a second time. Fix the cause before re-presenting; a row released into the same failing condition simply returns to quarantine.
Authorizations
JWT bearer token issued by the identity provider.
Headers
Tenant organization ID. Optional. The organization context is determined by the credentials you authenticate with; this header does not select or change it.
Client-supplied idempotency key, a UUID. Required: a request without it, or with a value that is not a UUID, is refused with 400 PBP-0012.
Path Parameters
Identifier of the quarantined webhook journal row (UUID), as reported by the PERMANENTLY_FAILED log line and metric.
"123e4567-e89b-12d3-a456-426614174000"

