HTTP Specification#

The SMS HTTP specification defines how DIDWW delivers inbound SMS messages to your systems over HTTP. It covers request formats, available variables, body formats, and failover handling.

To send outbound SMS over HTTP, use the Outbound SMS API.

Inbound SMS Specification

Technical details for receiving inbound SMS from DIDWW via HTTP.

Inbound SMS Specification
Outbound SMS API

Send outbound SMS to the DIDWW network over HTTP.

Outbound SMS API


Inbound SMS Specification#

The Inbound SMS service lets you receive text messages by having DIDWW forward them to your HTTP endpoint. Find out how requests are sent, which variables you can use, the formats supported for the request body, and key technical details such as retries and failover.


HTTP Request Details from DIDWW#

When a message is received on one of your DIDs, DIDWW will send an HTTP request to the Request URL configured in your SMS to HTTP IN Trunk.

Property

Description

HTTP Methods

Supported methods are GET, POST, and PUT.

Source IPs

Requests may originate from 46.19.209.214 or 185.238.173.74.

Connection Type

HTTPS (recommended) and HTTP are supported.

Note

Allow requests from 46.19.209.214 and 185.238.173.74 in your firewall.


Available Variables#

Variable

Description

{SMS_UUID}

The unique ID of the received message.

{SMS_SRC_ADDR}

The sender’s phone number or alphanumeric sender ID (source address), for more information see RFC 3986.

{SMS_DST_ADDR}

The DID number that received the SMS (destination address), for more information see RFC 3986.

{SMS_TEXT}

The raw text of the SMS message body.

{SMS_TEXT_BASE64_ENCODED}

The SMS message body, encoded using Base64.

{SMS_TIME}

The date and time the message was received, for more information see RFC 1123.

Note

You can use these variables to construct the Request URL, Query Parameters, Headers, and Body of the request in your trunk configuration.


Request Body Formats#

When DIDWW forwards an inbound SMS to your HTTP endpoint, the SMS data is placed in the body of the HTTP request. The format is selected in your trunk settings and determines how your server should parse the data.

Available formats:
  • RAW

  • JSON (application/json)

  • HTML URL Encoded (application/x-www-form-urlencoded)

  • HTML Multipart (multipart/form-data)

Note

Choose the format that matches how your endpoint is designed. For example, if your system expects JSON but receives URL encoded data, it will not parse correctly.


Technical Details#

If your endpoint does not respond with a 2xx status code, DIDWW will re-attempt to deliver the message until its Time To Live (TTL) of 3600 seconds (1 hour) expires.

The maximum size of an inbound SMS message is 64 KB.
Concatenated messages will be reassembled using User Data Header (UDH) before being delivered to your endpoint. Information about fragmentation will not be transmitted.