SMS Submit is a service for sending and receiving SMS with global coverage. An account in the SMS Submit service enables you to integrate SMS services in your own application using easy-to-use interfaces. It uses our own messaging gateway EMG.
Message flows
We support several different ways of getting messages into the SMS Submit service, and several ways for them to leave. To send an SMS, we support the following alternatives.
- Send it using SMPP or UCP. This is useful if you already have these protocols on your end.
- Send it using HTTP. This is useful for new clients.
- Send it as an SMS to a number from our number pool.
- Send it as an email, to an email address such as phonenumber@yoursubdomain.one.of.our.domains. You can define both the list of permitted senders and aliases for sending messages to a group. The latter is often used for sending alarms, for all employees in a particular office, etc.
The email alternative is often combined with our number pool. We then make a temporary mapping from a new number in this pool to the sender address of the email. When the recipient replies to the SMS, we convert this back to an email, making it possible to do bidirectional communication with email on one end and SMS on the other.
For the outgoing traffic, we support the following.
- It is sent to the recipient’s mobile phone.
- It is sent as an email to a predefined email address.
- It is sent as an HTTP POST to your application. This is useful for automatic processing of incoming messages, for example voting on TV shows, and is therefore most often combined with incoming messages as SMS.
All combinations of incoming and outgoing alternatives are possible, even though HTTP to HTTP probably is not too useful. All communication can use TLS 1.3.
Delivery reports are supported. They are either sent back on the same connection type as the incoming SMS if the protocol supports it (SMPP and UCP), or posted over HTTP.