API responses

Specific API response codes may be returned when send or receive operations fail. The most common codes are listed below. For interactive examples, see the API reference pages in the sidebar.

Success responses

Code	Description
`100`	Request successful. Message has been submitted for processing.

Success example

HTTP/1.1 200 OK
{
  "successful": true,
  "request_id": 67,
  "code": 100,
  "message": "Message Submitted Successfully",
  "valid": 1,
  "invalid": 0,
  "duplicates": 0
}

Client errors

Code	Description
`101`	Invalid phone number (`dest_addr` is invalid).
`102`	Insufficient balance to send SMS.
`104`	Missing required parameters.
`109`	Invalid or empty message content.
`110`	Message contains unsupported special characters.
`111`	Invalid Sender ID (not registered or inactive).
`112`	Scheduled time is in the past.
`113`	Invalid request format (JSON/XML).
`114`	Recipients exceed the maximum limit (1000).
`115`	Destination address is missing.
`116`	Missing or invalid reference ID.
`117`	Invalid scheduled time format (`YYYY-MM-DD HH:MM`).
`118`	Missing encoding type.
`119`	Missing recipients tag.
`120`	Invalid authentication parameters.
`121`	Sender ID format is invalid.
`122`	Duplicate Sender ID.
`123`	Template does not exist.

Server errors

Code	Description
`103`	Network timeout or internal server error.

HTTP status codes

HTTP status	Typical cause
`200`	Request accepted or completed successfully
`400`	Invalid request parameters, missing authorization header, or validation error
`401`	Invalid authentication — see example below
`404`	Invalid `request_id` or `dest_addr` on delivery report lookup

Invalid Sender ID example

HTTP/1.1 400 Bad Request
{
  "code": 111,
  "message": "Invalid Sender ID"
}

Authentication error example

HTTP/1.1 401 Unauthorized
{
  "code": 120,
  "message": "Invalid Authentication Parameters"
}

Missing authorization header example

HTTP/1.1 400 Bad Request
{
  "error": "No authorization headers"
}

Delivery report not found example

HTTP/1.1 404 Not Found
{
  "error": "Invalid request_id or dest_addr"
}

Rate limits

Beem may apply rate limits to protect platform stability. If you exceed allowed throughput, requests may be rejected or queued. Contact support@beem.africa for your account’s specific limits before high-volume production launches.

Delivery reports — poll message delivery status
Authentication — API Key, Secret, and access tokens
Sender ID registration — resolve error code 111

Getting Started

APIs

Success responses

Success example

Client errors

Server errors

HTTP status codes

Invalid Sender ID example

Authentication error example

Missing authorization header example

Delivery report not found example

Rate limits

​Success responses

​Success example

​Client errors

​Server errors

​HTTP status codes

​Invalid Sender ID example

​Authentication error example

​Missing authorization header example

​Delivery report not found example

​Rate limits

​Related

Success responses

Success example

Client errors

Server errors

HTTP status codes

Invalid Sender ID example

Authentication error example

Missing authorization header example

Delivery report not found example

Rate limits

Related