#Available Interfaces
Back to main page - Table of contents - Previous section - Next section
The SMS Gateway API have several different interfaces that you can choose to integrate towards. We generally suggest the REST API for both MT, MO and DR if you have no preference.
The different interfaces have some differences regarding what functionality is available, see table below:
| Interface Name | Outgoing (MT SMS) | Incoming (MO SMS) | Delivery Reports (DR) | Comments |
|---|---|---|---|---|
| REST API | Yes | Yes | Yes | Recommended |
| SOAP API | Yes | No | No | |
| HTTP(S) GET | Yes | Yes | Yes | Number of messages in each batch limited by max URL length |
| SMTP (email) | Yes | Yes | No | Not all parameters are available |
| SMPP | Yes | Yes | Yes | Only recommended if you have a pre-built SMPP client |
| TCP Socket | Yes | No | No |
It is possible to combine the different interfaces, for example it is possible to send MT messages using SOAP webservices, receive MO SMS using Rest API (HTTP POST with JSON or XML) and recieve delivery reports using HTTP(S) GET.
When integrating towards SMS Gateway, make sure that your client support the latest TLS standards (e.g. TLSv1.2) and support cipher suites that are considered secure.