![HTTP Codes](/assets/xml.2fdac585bc67aaebd157e6960732e00d7a865c38bb506fd6c9f9a9157985661c.9c1bb791.png)

## Response Codes

Elevate IQ APIs use standard HTTP response codes. Here are the most common codes you may encounter:

### 2xx Successful Responses

These responses confirm the request was expected and successful.

| Response Code | Description |
|  --- | --- |
| 200 OK | The request has succeeded. |
| 201 Created | The request has been accepted and resulted in a new resource being created. The newly created resource will be returned with a unique ID. |
| 204 No Content | The request was successful, but no body was returned. |


### 4xx Client Error Responses

These responses indicate an error with the request from the client. The response body will contain error details.

| Response Code | Description |
|  --- | --- |
| 400 Bad Request | The request could not be processed by the server, usually due to malformed syntax or server error. The response body will contain error details. |
| 401 Unauthorized | The client has not provided valid Authentication information or the user account making the request has been disabled. The response body will contain error details. |
| 403 Forbidden | The client has provided valid Authentication information, but does not have sufficient permission to access this resource. |
| 404 Not Found | The requested resource was not found. The response body will contain error details. |
| 405 Not Allowed | The HTTP method is not allowed for this resource. |
| 406 Not Acceptable | The content type specified was not acceptable. |
| 409 Conflict | The resource requested to be created already exists. |
| 415 Unsupported Media Type | The media/MIME type specified is not supported. |


### 5xx Server Error Responses

These responses indicate a server error.

| Response Code | Description |
|  --- | --- |
| 500 Internal Server Error | The server encountered an error while processing your request and failed. Please contact Elevate support. |


## Error Response Body

When a 4xx or 5xx response is returned, an error response body will typically be included with details about the error. The structure may vary but generally includes:


```json
{
  "error": "Bad Request",
  "message": "Validation failed for field 'customerName': must not be empty",
  "timestamp": "2026-01-08T12:00:00Z",
  "path": "/customers"
}
```

Multiple validation errors may be returned in a single response when applicable.

## Tips for Handling Errors

1. **Always check response codes** - Don't assume success; check the HTTP status code
2. **Parse error messages** - Error responses contain useful information for debugging
3. **Implement retry logic** - For 5xx errors, implement exponential backoff retry strategies
4. **Handle authentication failures** - Refresh tokens when receiving 401 responses
5. **Log errors with context** - Include request details when logging errors for support


## Need Help?

If you encounter persistent errors or need clarification:

- Review the [API Reference](/api) for endpoint-specific requirements
- Check the [How-to Guides](/pages/how-to-guides) for common integration patterns
- [Contact us](/pages/contact) for assistance