Skip Navigation
Log In Sign Up

Errors

·

Tupel uses standard HTTP status codes along with detailed error messages to help you identify and resolve issues with your API requests. This page provides a comprehensive guide to understanding and handling errors.

HTTP Status Codes

Code Description
200 OK - Your request was successful.
401 Unauthorized - No valid API key or Organization ID provided.
403 Forbidden - Your API key doesn't have permission to perform the requested action.
404 Not Found - The requested resource doesn't exist.
422 Unprocessable Entity - Request validation failed. The request contains invalid parameters.
429 Too Many Requests - You've exceeded the rate limit (60 requests per minute).
5xx Server Error - Something went wrong on Tupel's end (extremely rare). Our team is automatically notified of these errors.

Best Practices for Error Handling

  1. Check HTTP status codes first to understand the general category of the error.
  2. Examine the error message for specific details about what went wrong.
  3. Implement retry logic with backoff for rate limiting (429) and server errors (5xx).
  4. Log detailed error information in your application for easier debugging.
  5. Handle validation errors (422) by fixing the request parameters rather than implementing retries.

Support

If you're experiencing persistent issues or have questions about specific error messages, please contact support@tupel.com.

Error Response Format

All error responses follow a consistent JSON format:

{
  "detail": [
    {
      "type": "error_type",
      "loc": ["body", "field_name"],
      "msg": "A human-readable explanation of what went wrong."
    }
  ]
}

The error response contains:

  • detail: An array of error objects
  • type: The type of error (e.g., "missing", "value_error", "type_error")
  • loc: The location of the error, typically indicating the request part (body, query, path) and the specific field
  • msg: A human-readable error message explaining the issue