API Authentication, Errors, and Rate Limits

This article outlines the integration controls developers need to verify in TERA’s official API documentation before shipping production code.

Authentication

Confirm whether the supported method uses bearer tokens or another scheme and which account or plan can issue credentials. Never expose private tokens in public repositories or client-side code.

Permission Scope

Use the least privilege required for each integration and review whether tokens are scoped to an account, Workspace or operation.

HTTP Error Handling

Handle authentication failures, permission denials, missing resources, validation errors and server errors according to the actual status codes documented by TERA.

Rate Limits

Do not invent request quotas. Obtain the current rate limit, retry instructions and any response headers from TERA’s API reference.

Retry Safety

Implement exponential backoff only where appropriate and consider idempotency before retrying operations that create or delete resources.

Operational Security

Rotate compromised credentials promptly, redact secrets in logs and monitor integration activity for unexpected behavior.