> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stateset.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Tenant-wide SSE stream of every job's status events

> Tenant-wide event stream — receive status events for every job. Same SSE shape as /jobs/{id}/events but unscoped from a single job…

<Warning>
  **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](/api-reference/hosts) and obtain your deployment URL and credentials.
  Replace the example host if your provisioned service uses a different URL.
</Warning>

Tenant-wide event stream — receive status events for every job.

Same SSE shape as `/jobs/&#123;id&#125;/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

| Code | Meaning |
| - | - |
| `200` | 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. |

### Using this contract

Read the [source OpenAPI document](/spec/computer-use.json) for declared schemas and alternatives.
This page also includes documented corrections from the [spec overlays](https://github.com/stateset/docs/tree/main/spec/overlays).
Example IDs and values are illustrative; replace them with records from your workspace.

<RequestExample>
  ```bash cURL theme={null}
  curl --silent --show-error --fail-with-body --no-buffer --request GET \
    --url 'https://api.computer.stateset.app/api/v1/events/stream' \
    --header "X-API-Key: $STATESET_COMPUTER_USE_API_KEY"
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  "string"
  ```
</ResponseExample>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.