Skip to main content
When making API calls to Respan, you may encounter errors from two sources:
  1. Respan errors - Errors thrown by the Respan platform itself
  2. Provider errors - Errors from the underlying LLM provider (e.g., OpenAI, Anthropic)

​
Respan Exceptions

When Respan encounters an error, it will throw a RespanException. The error response will include details about what went wrong.

​
Common Respan Error Responses

​
401 Unauthorized

{
  "detail": "Your API key is invalid or expired, please check your API key at https://platform.respan.ai/platform/api/api-keys"
}

​
400 Bad Request

{
  "detail": "Invalid request format"
}

​
422 Unprocessable Entity

{
  "detail": "Validation error",
  "errors": {
    "field_name": ["Error message"]
  }
}

​
429 Too Many Requests

{
  "detail": "Rate limit exceeded",
  "retry_after": 60
}

​
500 Internal Server Error

{
  "detail": "Internal server error",
  "error_code": "INTERNAL_ERROR"
}

​
Provider Exceptions

When an error originates from the underlying LLM provider (e.g., OpenAI, Anthropic), Respan will surface the provider’s error response directly. The exception type will match the provider’s exception (e.g., OpenAIException for OpenAI errors).

​
OpenAI Errors

When using OpenAI models, you may encounter OpenAIException. The error response will be in OpenAI’s format: 
{
  "error": {
    "message": "Incorrect API key provided",
    "type": "invalid_request_error",
    "param": null,
    "code": "invalid_api_key"
  }
}

​
Anthropic Errors

When using Anthropic models, you may encounter AnthropicException: 
{
  "error": {
    "type": "authentication_error",
    "message": "Invalid API key"
  }
}