Trigger TED IN Poller
Use this endpoint to force one immediate JD inbound poll cycle for the current tenant. This is an operational endpoint intended to accelerate receipt of JD return messages without waiting for the scheduled poll interval. It does not require the X-Organization-Id header — the tenant is derived from the authenticated context.
Same-key retries replay the cached response instead of draining JD again. An in-flight duplicate is rejected with 409 by the route-level idempotency middleware.
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.
255Response
Indicates that the poll cycle completed. The outcome field reports the cycle result: success, empty, skipped_outside_window, skipped_busy, cancelled, or error.
Cycle outcome label. success and empty are terminal happy paths; skipped_* indicates the cycle did not run; cancelled and error indicate aborted work.
success, empty, skipped_outside_window, skipped_busy, cancelled, error "success"
Number of inbound messages drained and processed during this cycle.
x >= 03