### Input Error Response Example

Source: https://tollguru.com/toll-api-docs/content/after/errors-and-troubleshooting

An example of an error response triggered by malformed inputs or invalid CSV files.

```json
{
  "status": "ERROR",
  "code": "INPUT_ERROR",
  "value": "Invalid request. The From and To locations cannot be empty"
}
```

--------------------------------

### Routing Error Response Example

Source: https://tollguru.com/toll-api-docs/content/after/errors-and-troubleshooting

Returned when the algorithm cannot determine a valid route.

```json
{
  "status": 500,
  "code": "ROUTING_ERROR",
  "value": "No route exist"
}
```

--------------------------------

### Error Response Format

Source: https://tollguru.com/toll-api-docs/content/after/errors-and-troubleshooting

The standard structure for error responses returned by the API when a request fails.

```APIDOC
### Error Response Format

When an error occurs, the API returns a JSON object containing the status code, a machine-readable error code, and a descriptive value.

#### Response Example
```json
{
  "status": 500,
  "code": "TOLLING_ERROR",
  "value": "API call failed with status: 500 Internal Server Error"
}
```
```

--------------------------------

### Standard Error Response Format

Source: https://tollguru.com/toll-api-docs/content/after/errors-and-troubleshooting

The structure of a typical error response returned by the API.

```json
{
  "status": 500,
  "code": "TOLLING_ERROR",
  "value": "API call failed with status: 500 Internal Server Error"
}
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.