Ingest Via Api Key — POST /api/v1/stream/ingest
Ingest Via Api Key
Stream test results using only an API key — no /sessions ceremony.
Endpoint: POST /api/v1/stream/ingest
Authentication: Send a project-scoped API key with the stream:write scope in X-API-Key: <API key>. Access tokens are not accepted.
Parameters
Section titled “Parameters”| Name | In | Required | Type | Default | Description |
|---|---|---|---|---|---|
X-API-Key | header | no | string or null | API key, as an alternative to the access token (see Authentication). |
Request body
Section titled “Request body”| Content type | Body | Required |
|---|---|---|
application/json | LiveStreamIngestRequest | yes |
Responses
Section titled “Responses”| Status | Meaning | Body |
|---|---|---|
202 | Successful Response | LiveStreamIngestResponse (application/json) |
422 | Validation Error | HTTPValidationError (application/json) |
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: Live Stream
- Operation ID:
ingest_via_api_key_api_v1_stream_ingest_post - Source code:
backend/app/routers/stream.py, line 173 - Specification: OpenAPI JSON