Sendexa LogoDocs

SMPP API

Connect to Sendexa via the Short Message Peer-to-Peer (SMPP) protocol for high-throughput, asynchronous SMS messaging.

Sendexa supports SMPP version 3.4. SMPP is ideal for enterprise applications requiring persistent connections, high transaction volumes, and precise delivery receipt handling. By establishing an SMPP bind, you maintain an always-on connection to our gateways.

Connection Details
Use these parameters to configure your SMPP client (ESME).
ParameterValueDescription
Host / IPsmpp.sendexa.coThe primary endpoint for all SMPP connections.
Port (Plaintext)2775Standard unencrypted connection port.
Port (TLS/SSL)2776Encrypted connection port (Recommended).
System IDYour Client IDFound in your Sendexa dashboard under API Credentials.
PasswordYour Client SecretYour corresponding secure secret or API key.
System TypesendexaOptional identifier for your connection type.

Supported Bind Types

Transceiver
TRX
Supports both sending messages and receiving delivery reports on a single connection. (Recommended)
Transmitter
TX
Dedicated connection strictly for submitting outbound messages to the Sendexa network.
Receiver
RX
Dedicated connection strictly for receiving delivery receipts (DLRs) and inbound messages.

Standard PDU Operations

Submitting Messages
Used by the client to send a short message to the SMSC.

The submit_sm PDU is used to send messages. To receive delivery receipts, ensure the registered_delivery flag is set to 1.

Important Parameters:

  • source_addr: Your Sender ID (alphanumeric or numeric).
  • destination_addr: The recipient's phone number in international format.
  • data_coding: 0 for ASCII/Default, 8 for UCS2 (Unicode).
  • registered_delivery: Set to 1 to request a DLR.

Best Practices

Window Size (Asynchronous Sending)
To achieve high throughput, send multiple submit_sm requests before waiting for their corresponding submit_sm_resp. A typical window size is between 10 and 50 unacknowledged messages.
Throughput Limits
Your SMPP connection is rate-limited based on your account's allocated Transactions Per Second (TPS). Exceeding this limit will result in ESME_RTHROTTLED (0x00000058) errors.