Replay TED IN Backlog
Use this endpoint to force one immediate replay pass over persisted, unprocessed JD inbound messages for the current tenant. Unlike /ted-in/poll, this route does not read JD’s destructive queue — it only reprocesses durable backlog rows already persisted locally.
Use the X-Idempotency header for guaranteed deduplication.
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.
Authorizations
JWT Bearer token authentication. The token must include a tenantId claim that matches the X-Organization-Id header.
Headers
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.
255Response
Indicates that the replay pass completed. The outcome field reports the cycle result and replayed is the number of backlog rows reprocessed.
Replay outcome label.
success, empty, skipped_outside_window, skipped_busy, cancelled, error "success"
Number of persisted backlog rows reprocessed during this pass.
x >= 02
The tenant for which the replay pass ran, when available.
"11111111-1111-1111-1111-111111111111"

