Documentation Index
Fetch the complete documentation index at: https://docs.envless.cloud/llms.txt
Use this file to discover all available pages before exploring further.
Envelope
Every response — success or error — uses the same shape:| Field | Meaning |
|---|---|
success | true for 2xx, false otherwise. |
code | Mirrors the HTTP status code. |
message | Human-readable description — safe to log, not always safe to show to end users. |
data | Resource payload on success, null on error. |
The HTTP status and the envelope code always agree. Branch on either.
Status codes
| Status | Meaning | When you’ll see it |
|---|---|---|
200 | OK | Successful read. |
400 | Bad Request | Invalid query parameters (e.g. limit=99999). |
401 | Unauthorized | Missing, malformed, or revoked API key. |
404 | Not Found | Resource doesn’t exist, or your key can’t see it. |
500 | Internal Server Error | Unexpected — retry with backoff, then check status.envless.cloud. |
404 vs 403
The API returns 404 — not 403 — when a resource exists but your key can’t see it. This avoids leaking the existence of projects, environments, or variables across workspaces.
If you’re sure the resource exists and your key should reach it, double-check the workspace association in the dashboard.
Handling errors
Request IDs
Every response includes a _req field with the request ID and server-side timing:
Include reqId when you contact support — it points us at the exact request in our logs.