Errors & limits
Errors are returned as JSON with an error field and a matching HTTP status.
Status codes
| Status | error | Meaning |
|---|---|---|
| 200 / 201 | — | Success. |
| 400 | invalid_path | The object path was empty or malformed. |
| 401 | unauthorized | Missing or wrong secret. |
| 403 | forbidden | The key lacks the required scope (e.g. no write). |
| 404 | not_found | No object at that path. |
| 413 | too_large | Object exceeds the per-object size cap. |
| 507 | quota_exceeded | The write would exceed the key's quota (live keys only). |
Limits
- Object size — up to 256 MB per object. Split larger data into parts.
- Quota — live keys count against your plan; a full key returns
507. Test keys are quota-free. - Scopes —
read,write,delete; enforced per request.
Heads upTreat
507 quota_exceeded as a signal to upgrade the plan or prune old objects — writes will keep failing until there is room.