Skip to main content
Every Tellus Open Platform API response — successful or not — follows a consistent envelope. Errors include a numeric code, a human-readable message, and (optionally) a details block with diagnostic context.

Error envelope

The 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

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:
  • 1001 invalid parameters
  • 1002 missing parameter
  • 2001 invalid token (after one refresh attempt)
  • 2003 permission denied
  • 3001 resource not found
  • 4001 conflict

Reporting issues

If you encounter persistent 9001 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 your client_secret)
The Tellus platform team typically responds within one business day.