Error Response Format
All TensorOne API errors follow a consistent JSON format:HTTP Status Codes
4xx Client Errors
400 Bad Request
The request was invalid or missing required parameters.401 Unauthorized
Authentication failed or API key is invalid.403 Forbidden
API key lacks required permissions for the requested resource.404 Not Found
The requested resource doesn’t exist.409 Conflict
Request conflicts with current resource state.422 Unprocessable Entity
Request is well-formed but contains semantic errors.429 Too Many Requests
Rate limit exceeded.5xx Server Errors
500 Internal Server Error
Unexpected server error occurred.502 Bad Gateway
Upstream service is unavailable.503 Service Unavailable
Service is temporarily overloaded or under maintenance.Domain-Specific Errors
Cluster Errors
CLUSTER_CREATION_FAILED
CLUSTER_START_TIMEOUT
Endpoint Errors
ENDPOINT_EXECUTION_FAILED
ENDPOINT_TIMEOUT
Training Errors
TRAINING_DATA_INVALID
Payment Errors
INSUFFICIENT_CREDITS
PAYMENT_METHOD_DECLINED
Error Handling Best Practices
1. Implement Retry Logic
2. Graceful Error Handling
3. Validation Before Requests
4. User-Friendly Error Messages
Debugging Tips
1. Log Request IDs
Always log therequest_id
from error responses for support inquiries:
2. Monitor Error Patterns
Track error frequencies to identify patterns:3. Validate Responses
Always validate API responses:Getting Help
When contacting support, include:- Request ID from the error response
- Timestamp of the error
- Full error response (sanitized of sensitive data)
- Code snippet that produced the error
- Expected behavior vs actual behavior
Never include API keys or sensitive data in support requests or logs.