Stream the changes of several sandboxes
Stream the changes of up to 100 sandboxes as server-sent events.
- Each
sandboxevent carries the sandbox exactly asGET /v1/sandboxes/{idOrName}returns it to the caller. - The stream sends every sandbox at once, then again each time its response changes.
- A
removedevent says that the stream sends no more events for a sandbox: it reached the deleted state, or the caller can no longer read it. - Close the stream after the last
removedevent. A browserEventSourceopens a closed stream again by itself. - A
pingevent arrives every 25 s when no other event arrives. - The caller must be able to read every sandbox when the stream opens.
- The stream ends after the last
removedevent.
Authorization
apiKey API key starting with tektona_. Create one at app-dev.tektona.ai under API Keys.
In: header
Query Parameters
Sandbox ID (ULID). Repeat the parameter for each sandbox.
1 <= items <= 100Response Body
text/event-stream
application/problem+json
curl -X GET "https://example.com/v1/sandbox-events?id=string"[ { "data": {}, "event": "ping", "id": 0, "retry": 0 }]{ "detail": "Property foo is required but is missing.", "errors": [ { "location": "string", "message": "string", "value": null } ], "instance": "https://example.com/error-log/abc123", "status": 400, "title": "Bad Request", "type": "https://example.com/errors/example"}Stream the changes of a sandbox GET
Stream the changes of one sandbox as server-sent events. - Each `sandbox` event carries the sandbox exactly as `GET /v1/sandboxes/{idOrName}` returns it to the caller. - The stream sends every sandbox at once, then again each time its response changes. - A `removed` event says that the stream sends no more events for a sandbox: it reached the deleted state, or the caller can no longer read it. - Close the stream after the last `removed` event. A browser `EventSource` opens a closed stream again by itself. - A `ping` event arrives every 25 s when no other event arrives. - The stream ends after the `removed` event.
Get sandbox stats history GET
Get the CPU, memory and disk usage of a sandbox over time. The server keeps a sample every 3 s for 7 days and groups the samples to a step that gives at most 1,500 points. The answer also lists the periods in which the sandbox was paused, and the changes of its size that took effect, in the range. The live stream at `/v1/sandboxes/{idOrName}/stats/live` sends the newest samples.