Retry DLQ Message
Use this endpoint to re-publish a specific DLQ message back to the main webhook processing queue. Only messages belonging to the caller’s tenant are eligible. The tenant is derived from the bearer JWT (tenantId claim).
This route is only mounted when authentication is enabled and a DLQ inspector is configured. Otherwise it is not exposed and any request is rejected with 503.
Authorizations
JWT Bearer token authentication. The tenantId is derived from the bearer token or authenticated request context and is not supplied through X-Organization-Id.
Headers
Required idempotency key for safe retries. Use a UUID v4 or unique business identifier. If the same key is sent again and the original request was already processed, the cached response is returned.
See Retries and idempotency for details.
255Path Parameters
The DLQ message identifier to retry.

