Skip to main content
GET
Confirm your deployment before running this request. This page describes an API contract; a published reference does not establish hosted availability. Check the dated host report and obtain your deployment URL and credentials. Replace the example host if your provisioned service uses a different URL.
Tenant-wide event stream — receive status events for every job. Same SSE shape as /jobs/{id}/events but unscoped from a single job. Useful for tenant dashboards that want to render an in-flight panel without fanning out one connection per job. Events are filtered server-side: only events whose id belongs to the calling tenant are surfaced. The first lookup for a previously unseen job hits the DB; subsequent events for the same job are served from an in-stream cache. Behaviour:
  • 15s keepalive comments to survive proxies.
  • 30-min lifetime cap; client should reconnect after event: timeout.
  • No initial snapshot (the per-tenant set could be huge); use GET /jobs?status=running if you need a starting state.

Response

Returns text/event-stream — Server-Sent Events. Parse SSE frames; this is not a JSON response body. Keepalive comments and named timeout/error events are separate from JSON data frames.

Status codes

Using this contract

Read the source OpenAPI document for declared schemas and alternatives. This page also includes documented corrections from the spec overlays. Example IDs and values are illustrative; replace them with records from your workspace.
Last modified on September 21, 2026