BroadNet
Reference·/error-codes

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.

Browsable·Updated September 2026·Section 10 of 15Developer Hub

Overview

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

Copy, paste, replace the placeholders — these examples call the production API as written.

ExceptionResponsejson
{
  "status": 400,
  "error": "Bad Request",
  "message": "…",
  "errorCode": "…",
  "requestUri": "/sms/sendSms"
}
401 Unauthorized (API gateway)json
{
  "error": "Unauthorized",
  "message": "Missing Authorization token"
}
Test access · reply within one business day

Request test access and build with confidence.

We reply within one business day with test credentials. Then install the TypeScript SDK or call the REST API from any language, and send your first test message to your own number.

$npm install @broadnet/cpaas-sdk axiosready