Every Tellus Open Platform API response — successful or not — follows a consistent envelope. Errors include a numericDocumentation Index
Fetch the complete documentation index at: https://developers.telluspowergroup.com/llms.txt
Use this file to discover all available pages before exploring further.
code, a human-readable message, and (optionally) a details block with diagnostic context.
Error envelope
code is the canonical machine-readable identifier. Use it for branching logic; never parse message strings — message text may change without notice.
Error code reference
| Code | HTTP | Description | Recommended action |
|---|---|---|---|
| 0 | 200 | Success | — |
| 1001 | 400 | Invalid request parameters | Check parameter format and ranges |
| 1002 | 400 | Missing required parameter | Inspect details.field, supply the missing value |
| 2001 | 401 | Unauthenticated or invalid token | Obtain a valid token via /v1/operator/oauth/token |
| 2002 | 401 | Token expired | Refresh the token and retry the request |
| 2003 | 403 | Permission denied | Verify the client_id has the required scope (read or write) |
| 3001 | 404 | Resource not found | Check the resource ID — it may have been deleted or be owned by a different operator |
| 4001 | 409 | Resource conflict | E.g., a device with that sn is already registered |
| 5001 | 429 | Too many requests | Apply backoff (see Rate Limits guide) |
| 9001 | 500 | Internal server error | Retry with backoff; if persistent, contact support |
Retry strategy
For transient errors, an exponential-backoff retry with jitter is recommended:Errors not to retry
The following codes indicate permanent problems with the request itself; retrying them will produce the same result. Surface them to the caller for inspection rather than retrying:1001invalid parameters1002missing parameter2001invalid token (after one refresh attempt)2003permission denied3001resource not found4001conflict
Reporting issues
If you encounter persistent9001 errors or unexpected behaviour, please report them to support@telluspowergroup.com. Include:
- The full request URL, method, and request body (with secrets redacted)
- The full response including all headers
- A timestamp range during which the issue occurred
- Your
client_id(not yourclient_secret)