---
title: "Stream Operation Events"
method: GET
path: "/v1/operations/{operation_id}/stream"
tags: ["Operations"]
---

# Stream Operation Events

`GET /v1/operations/{operation_id}/stream`

## Request

- Base URL: `https://api.robosystems.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.robosystems.ai/v1/operations/{operation_id}/stream`
- Auth: one of:
  - API key in header `X-API-Key`
  - HTTP bearer

Server-Sent Events stream for real-time operation progress. Use `from_sequence` to replay missed events on reconnect. Max 5 concurrent SSE connections per user. Consumes no credits.

## Path parameters

- `operation_id` string, required: Operation identifier from initial submission

## Query parameters

- `from_sequence` integer: Replay stored events from this sequence number, then stream live ones. A running operation replays nothing at 0 (live events only); a settled one replays its history from here (0 = all) and closes.
- `token` string, nullable: JWT token for SSE authentication

## Headers

- `authorization` string, nullable

## Response `200`

SSE stream — Content-Type: text/event-stream

- unknown

## Other responses

- `400`: Invalid request
- `401`: Authentication required
- `403`: Access denied
- `404`: Resource not found
- `422`: Validation Error
- `429`: Rate limit exceeded
- `500`: Internal server error

---

[API](https://skmtc.dev/robosystems/apis/robosystems-api.md) · [All operations](https://skmtc.dev/robosystems/apis/robosystems-api/llms.txt) · [OpenAPI document](https://skmtc.dev/robosystems/apis/robosystems-api/revisions/e661e2d5ca6a?raw)