# Troubleshooting Rooms API error responses

This topic lists all the possible errors you might encounter while using the Rooms API and how to resolve them.

## Working with errors

This section captures a list of common HTTP errors you might encounter and possible solutions to fix them.

| HTTP Error Code | OTA Error Code | Description | Reason and Possible Fix |
|  --- | --- | --- | --- |
| HTTP 400 Bad Request | 320 | Invalid value | The API returns `errors.details` and `errors.description` that captures which part of the request body contains invalid values and a description to help you troubleshoot the error. See the list of Rooms API [validation rules](/connectivity/docs/rooms-api/rooms-api-validations#rooms-api-validation-rules) and respective error descriptions.  To know more about the exact fields with invalid values, most errors will include values within `errors.details.fields`. |
| HTTP 400 Bad Request | 321 | Required field missing | Use the `errors.details` and `errors.description` field to identify the missing required fields and a description to help you troubleshoot the error.  To know more about the exact fields with missing values, parse the `errors.details.fields`. |
| HTTP 400 Bad Request | 394 | Invalid item | Can occur when you specify an unknown parameter in the request. Make sure to specify the right parameters. Check for typos. |
| HTTP 400 Bad Request | 450 | Unable to process | Can occur due to one of the following reasons: incorrect endpoint URL/HTTP method or invalid JSON body. Make sure to use the correct endpoint URL/HTTP method or check if the request has a valid JSON body. |
| HTTP 401 Unathorized | - | Access denied | The request contains invalid authentication credentials.  Provide the correct authentication details. |