SMS gateway configuration
The messaging service supports two ways of sending SMS messages, by integrating with:
-
A custom API
CM.com configuration
The default integration for the messaging service is with CM.com. CM.com requires a product token to send SMS messages via its gateway. To be able to use it, the product token must be specified in the configuration screen.
You can also specify the default sender, which is used as the SMS message sender when the request to send the message does not contain a sender. This default sender can be a phone number, a short code, or the name of the sender.
Custom API configuration
The custom API integration is meant to be used with any service that conforms to the OneWelcome Identity Platform API specification. See the outgoing API reference for details about the format and supported HTTP methods.
To configure the custom API integration, you must specify the URL of the endpoint to which the messaging service forwards the data. You can additionally specify the credentials if the endpoint is protected by basic authentication. You can also specify any other additional parameters that are passed to the custom endpoint along with the other notification related parameters, like content, sender, receiver, and so on.
The messaging service issues HTTP POST requests to the specified endpoint with all data required to send out SMS notifications. The responsibility to actually send out the message is moved to the custom API handler.
