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.
Documentation Index
Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
Use this file to discover all available pages before exploring further.
JWT Bearer token authentication. The token must include a tenantId claim that matches the X-Organization-Id header.
Organization ID used as the tenant identifier. All data is scoped to this organization. Must match the JWT tenantId claim when authentication is enabled.
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.
255The DLQ message identifier to retry.