Skip to main content
This section describes how to send requests from your Client Application to the Messaging Platform (MP) and interpret the responses.

​
Request flow

The client issues an HTTP GET or POST request to the platform. MP returns either an HTTP error code or HTTP 200 OK, in which case the response body contains additional status information.
Use POST rather than GET. GET query strings can exceed size limits and may be truncated by proxies.

​
Send endpoints

All endpoints accept the same form parameters. See the Parameters reference for the full list.

​
Required parameters

​
Response formats

​
Plain text (default)

When HTTP status is 200, the response body contains two or three lines:
  1. Message ID (numeric), or -1 if the request failed
  2. Status code — 0 for success; otherwise a numeric error code
  3. Status text (optional) — human-readable error description
Success example:
Failure example:
See API responses for HTTP-level errors. Platform-level failures may still return HTTP 200 with a failure status in the body (message ID -1).

​
Common status codes

​
JSON response

​
XML response

​
Persistent HTTP connections

The messaging platform allows HTTP connections to remain open to increase throughput. To maintain a persistent connection:
  • Do not specify Connection: close in your HTTP request
  • Do not close the connection after sending a message
  • Read the response data for each submission before sending the next request
Multiple GET or POST requests can be submitted over the same connection.

​
Sample code

Sample implementations in PHP, C#/.NET, Java, Python, and Node.js are available on GitHub: beem-sms-txn-api-sample — send