> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://bcdtravel.ferndocs.com/itinerary/guides/introduction/common-error-responses/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://bcdtravel.ferndocs.com/_mcp/server.

# Common error responses

We always respond to request failures with an HTTP status code and appropriate error details in the response body. This allows your application to programmatically resolve errors and provide inline error messaging within your application when appropriate.

## Error response format

```json
{
  "code": 400,
  "status": "error",
  "messages": [
    "Bad Request: tripId is not found or has incorrect format."
  ]
}
```

## Common error codes

| Status Code | Description                                                                         |
| ----------- | ----------------------------------------------------------------------------------- |
| `400`       | Bad Request — The request was malformed or a required parameter is missing/invalid. |
| `401`       | Unauthorized — Authentication failed or the access token is expired.                |
| `403`       | Forbidden — The API is disabled for the consumer.                                   |
| `404`       | Not Found — The requested resource was not found.                                   |
| `500`       | Server Error — An internal server error occurred.                                   |

> Understand the error codes and responses returned by the Itinerary API.