> ## Documentation Index
> Fetch the complete documentation index at: https://developer.obiex.finance/llms.txt
> Use this file to discover all available pages before exploring further.

# Errors

> Understanding API error responses

When an API request fails, Obiex returns a standard error response with relevant information about what went wrong.

## Error Response Format

```json theme={null}
{
  "message": "Error description",
  "errors": [
    {
      "message": "Account has been disabled. Try again in 15 minutes"
    }
  ]
}
```

## Common Error Codes

| Code                  | HTTP Status | Description                       |
| --------------------- | ----------- | --------------------------------- |
| UNAUTHORIZED          | 401         | Invalid or missing authentication |
| FORBIDDEN             | 403         | Insufficient permissions          |
| NOT\_FOUND            | 404         | Resource not found                |
| VALIDATION\_ERROR     | 422         | Invalid request parameters        |
| RATE\_LIMIT\_EXCEEDED | 429         | Too many requests                 |
| INTERNAL\_ERROR       | 500         | Server error                      |

## HTTP Status Codes

| Status | Meaning               |
| ------ | --------------------- |
| 200    | Success               |
| 201    | Created               |
| 400    | Bad Request           |
| 401    | Unauthorized          |
| 403    | Forbidden             |
| 404    | Not Found             |
| 422    | Validation Error      |
| 429    | Too Many Requests     |
| 500    | Internal Server Error |

## Handling Errors

```javascript theme={null}
try {
  const response = await fetch('https://api.obiex.finance/addresses/me/broker', {
    headers: {
      'Authorization': 'YOUR_API_KEY'
    }
  });
  
  if (!response.ok) {
    const error = await response.json();
    console.error('API Error:', error.message);
    return;
  }
  
  const data = await response.json();
} catch (err) {
  console.error('Network error:', err);
}
```