# Error code reference

> Every error code returned by the BroadNet API, what it means, and how to handle it. Updated whenever new codes are added.

- Canonical URL: https://www.broadnet.me/developers/error-codes
- Language: en
- Last updated: 2026-10-21
- Publisher: BroadNet (https://www.broadnet.me)

The BroadNet REST API reports errors with a standard HTTP status code and a JSON body called ExceptionResponse, with five fields: status, error, message, errorCode and requestUri. Match on the HTTP status first, then on errorCode. One exception: a missing or invalid Bearer token is rejected earlier, at the API gateway, with a 401 whose body has only error and message.

## Status codes

400 means a validation error or a missing required field: fix the request. 401 means the Bearer token is missing or invalid, and 403 that it is not allowed to call the operation: fix the token. 500 is an unexpected server error and 502 means an upstream provider rejected the call: retry with exponential backoff. SMPP binds return standard SMPP command_status codes instead.

## Examples

### ExceptionResponse

```json
{
  "status": 400,
  "error": "Bad Request",
  "message": "…",
  "errorCode": "…",
  "requestUri": "/sms/sendSms"
}
```

### 401 Unauthorized (API gateway)

```json
{
  "error": "Unauthorized",
  "message": "Missing Authorization token"
}
```

## Related

- [problem+json errors & pagination standard](https://www.broadnet.me/reference/api-errors-and-pagination)