HTTP channel (SMS, WhatsApp, Etc)
Use the HTTP channel to send SMS messages over the internet in a fast and simple way. Some providers, such as Twilio, only support HTTP.
Find more information about channels in general here.
To use the HTTP channel, you need a subscription with an SMS provider or aggregator.
Provider presets
When creating a new HTTP channel, you can select one of the provider presets.
Create HTTP Channel
Provider presets include default settings for known HTTP providers such as Twilio and Infobip. This means you only need to enter your account details to complete the configuration.
After selecting a provider preset and entering your details, you can continue through the wizard to verify the configuration and click Finish when you are done.
The HTTP channel wizard automatically keeps provider presets up to date when it starts. Select the Auron test or demo preset to receive 10 free SMS messages for testing.
Custom connection, parsing responses, delivery reports, and incoming messages
If your provider already has a preset available, you can skip this section.
If there is no preset available, select “Custom Settings” in the provider preset box. This allows you to configure any HTTP provider with Auron Omni.
You can find an overview of all configurable settings in the section below.
An important part of configuring a custom HTTP channel is parsing the HTTP response body, delivery reports, and incoming messages. In the HTTP channel, these are handled in the same way, as shown in the “Receive” page below:
Create HTTP Channel – Receive
Whenever a text body is parsed, you must specify:
- The structure of the text. This can be:
- Form or GET parameters
- XML structured text
- JSON structured text
- The container path. This is important if the body contains multiple messages
- The path for each required field. Paths depend on the format:
- An example text. This is optional but useful for testing your paths
Parsing example
An example is receiving SMS messages from Infobip where a single callback can contain multiple messages. The payload is structured in JSON like this:
{
"results": [
{
"messageId": "817790313235066447",
"from": "385916242493",
"to": "385921004026",
"text": "QUIZ Correct answer is Paris",
"cleanText": "Correct answer is Paris",
"keyword": "QUIZ",
"receivedAt": "2016-10-06T09:28:39.220+0000",
"smsCount": 1,
"price": {
"pricePerMessage": 0,
"currency": "EUR"
},
"callbackData": "callbackData"
}
],
"messageCount": 1,
"pendingMessageCount": 0
}The messages are contained in the “results” array. This means the container JSONPath must be:
$.results.*
This selects all result items. Each item represents a message object with its own fields.
When a container path is used, all field paths are relative to the selected items. For example, the message body is:
$.text
If you have trouble configuring your provider, please contact us.
Settings
From Address: This is the default sender address with TON and NPI values. If the sender address in the SMS message is empty, the HTTP channel uses this value.
| Property | Description |
| Send URL | The URL of the HTTP server. This must start with http or https depending on whether TLS is used. The URL may contain placeholders. Use the magnifier button (????) to edit the URL and insert placeholders. Placeholders are replaced with SMS fields when sending. |
| Use Post | Enable this option to send a POST body. Check your provider documentation to see if this is required. |
| Post Body | The body of the HTTP request. It may contain placeholders. Use the magnifier button (????) to edit and insert placeholders. Placeholders are replaced with SMS fields when sending. |
| Content Type | Optional content type header. Common values are:
|
| Public IP | Your public IP address. This is required when using %DLRURL% or %MEDIAURL% placeholders so the provider can reach your server. |
| Support delivery reports | Enable this if you want to support delivery reports. Your provider must be able to reach your server. |
| Local Endpoint | The endpoint where your provider can reach your system. This is required when:
Port forwarding may be required. Use “Configure…” to start the NetSh Express Setup. |
| Parse Response | Enable this when the response contains important data such as a message reference. |
| Response Has | Use this if the response is not structured. It checks whether the response contains or does not contain a specific string. |
| Delivery Reports | Defines how delivery reports are parsed. Available when delivery reports are enabled. |
| Receive | Defines how incoming messages are parsed. Available when receiving is enabled. |
| Use HTTP Authentication | Enable if your provider requires a username and password. |
| Authorization | Specify an API key or bearer token for the HTTP Authorization header. |
| HTTP Authentication | Username and password for HTTP authentication. |
| Use Proxy | Configure proxy settings if required. By default, system internet settings are used. |
| Service Type | Default system type. Used when the SMS message does not specify one. |