Stream Invocation Events — GET /api/v1/agents/invocations/{invocation_id}/events
Stream Invocation Events
Progress of one invocation as server-sent events, until its run finishes.
Endpoint: GET /api/v1/agents/invocations/{invocation_id}/events
Authentication: Pass the single-use stream ticket issued for this invocation as the ticket query parameter. Browsers cannot send an Authorization header to an event stream, so the ticket replaces it.
Parameters
Section titled “Parameters”| Name | In | Required | Type | Default | Description |
|---|---|---|---|---|---|
invocation_id | path | yes | string (uuid) | ||
ticket | query | yes | string |
Request body
Section titled “Request body”No request body.
Responses
Section titled “Responses”| Status | Meaning | Body |
|---|---|---|
200 | Successful Response | Not documented (application/json) |
422 | Validation Error | HTTPValidationError (application/json) |
Response fields not documented. The API specification does not describe the body of every response this endpoint returns, so this page cannot list those fields. The body is not empty. To see it, call the endpoint on your own installation. All endpoints with undocumented responses.
It can also return 401 if your credential is missing or expired, 403 if your credential does not allow this request, and 404 if the item does not exist or you cannot see it. Your role, your project membership and the key’s scope decide what a credential allows. See Errors and retries.
More details
Section titled “More details”- Group: Agent Invocations
- Operation ID:
stream_invocation_events_api_v1_agents_invocations__invocation_id__events_get - Source code:
backend/app/routers/agent_invoke.py, line 758 - Specification: OpenAPI JSON