REST (REpresentational State Transfer) uses the HTTP protocol (HTTPS) for conveying SMS operations. A REST account can easily be obtained for using the Tyr SMS Gateway. REST uses JSON to carry the parameters that relate to the REST operation that you are performing.
There are a number of different languages that can be used for sending and receiving SMS. Languages included in our tutorials that can be used for sending SMS with REST are:
REST API requirements and resources
In addition to the requirements of the chosen language, the following are required to send SMS with REST:
- REST API Key - API key for the REST SMS API of the Melrose Labs Tyr SMS Gateway
Other APIs covered in our tutorials that can be used for sending and receiving SMS include: SMPP
Using in production
Whether it is REST or another API, you can send SMS and receive SMS between applications and mobiles for a wide range of uses with any of the trusted and reliable CPaaS services from Melrose Labs. Take a look at our Messaging, SMS gateway and Bulk SMS solutions, and sign-up for a Developer account on our Tyr SMS Gateway service to try us out.
We provide a wide range of CPaaS services and infrastructure to organisations, including cloud platforms that enable you to run your own SMS gateway.
Get in contact with us to find out more about CPaaS voice, messaging, video and identity from Melrose Labs.
For testing your application's SMS support when using the SMPP protocol, we recommend starting with the Melrose Labs SMSC Simulator service to simulate SMS message delivery to mobiles (MT SMS) and simulate SMS messages from mobiles (MO SMS). The SMSC Simulator supports SMPP v3.3, v3.4 and v5.Get SMPP account for SMSC Simulator >
For live testing and delivery to mobiles, use the reliable and dependable Melrose Labs Tyr SMS Gateway for A2P, P2A, bulk, wholesale and business SMS, text marketing and other uses. The Melrose Labs Tyr SMS Gateway supports REST and SMPP APIs.Get Tyr SMS Gateway account >