Ingest Http Exchanges — POST /api/v1/stream/http-exchanges
Ingest Http Exchanges
The captured HTTP exchanges of ONE live test (opt-in capture).
Endpoint: POST /api/v1/stream/http-exchanges
Authentication: Send a signed-in user’s access token in Authorization: Bearer <access token>, or an API key in X-API-Key: <API key>.
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 | LiveHttpExchangesIn | yes |
Responses
Section titled “Responses”| Status | Meaning | Body |
|---|---|---|
202 | Successful Response | LiveHttpExchangesResponse (application/json) |
422 | Validation Error | HTTPValidationError (application/json) |
Errors this endpoint returns, read from its source code:
403, with the message “This API key is restricted to a different project”404, with the message “Session not found”
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_http_exchanges_api_v1_stream_http_exchanges_post - Source code:
backend/app/routers/stream.py, line 218 - Specification: OpenAPI JSON