The environment's own workloads' logs
GET
/v1/organisations/{id}/environments/{envId}/logsOperation environments.logs · since 2026-11-05 · stable
Needs a session withreadscopeAnswers200 OK
{ "components", "lines": [{ "at", "component", "level", "text" }], "truncated" }.
Logs are read inside the environment, so each read takes a moment. 503 busy and 502 logs_unavailable can be retried after a pause.
Path parameters
- idstring (uuid)required
- The organisation id.
- envIdstring (uuid)required
- The environment id.
Query parameters
- componentstringoptional
- Only this component.
- levelstringoptional
- "error", "warn", "info" or "debug".
- sincestringoptional
- How far back, like 30m, 2h or 1d (default 1h).
- limitinteger, 1 to 5000optional
- Lines at most (default 500).
- formatstringoptional
- "json" (default) or "text".
Errors
Every error is { "error", "message", "detail"? } (Errors and references). Besides the codes any route can answer, this one refuses with:
- busy
- not_ready
- logs_unavailable
GET/v1/organisations/{id}/environments/{envId}/logs
curl "https://api.rykloud.com/v1/organisations/$ORG_ID/environments/$ENV_ID/logs" \
-H "Authorization: Bearer $RYKLOUD_TOKEN"With the rykloud CLI
rykloud envs logs [ENV] [flags]Command reference: rykloud envs logs