Send to everyone, connect individually

FAQs

• What is a cloud-based SMS service?

  A cloud service is a service provided to clients on demand over the internet from the cloud computing provider’s servers (hardware). This removes the need for a client to have their own on-premise servers to host and run the software.
  
  A cloud-based SMS service is what we at Sinch offer, the services are accessed through our SMS messaging APIs and web tools.
  
  Check out our Developer area to find out more about our easy to use APIs to send SMS, and if your ready to go and don't need to integrate, sign up and get started with our web tool, Connect.
  

• How do I receive SMS message replies?

  You will need to purchase an inbound SMS number to receive replies. Check out our Numbers page too . If you already have a Sinch SMS account, please contact Support or your Account Manager and we'll help you get this sorted.
  
  Once an inbound SMS number has been configured on your account, you will be able to see replies in the ‘SMS response service’ tab.
  

• REST API - How to send your first message

  How to set up using the REST API
  
  There are many ways to make API calls to our SMS REST API. Here are some popular methods:
  
  Use a free HTTP request GUI, such as “Fiddler” – http://www.telerik.com/download/fiddler
  
  Use a web browser extension like “Postman” –https://www.getpostman.com
  
  Use a command line, such as “cURL” – http://curl.haxx.se/
  
  Send a message
  
  Now you’re ready to submit a message to the “batches” endpoint:
  
  HTTP method – Set the HTTP method to “POST”
  
  Host and endpoint – Set the host and endpoint, with your service username in place of {service_username}:
  
  https://api.sinch.com/xms/v1/{service_username}/batches
  
  Header – In the header, enter your authentication token and set the content type to JSON:
  
  Authorization: Bearer {authentication_token}
  
  Content-Type: application/json
  
  Body – Enter the following JSON body, where {your_phone_number} is the recipient phone number, including the country code:
  
  {“from”: “Sinch”,
  
  “to”: [“{your phone number}”],
  
  “body”: “Hi this is my first message using Sinch's SMS REST API” }
  
  Submit the request
  
  All you need to get started is your service username and API SMS token, which you can achieve in just a few clicks. Simply log into the Sinch Customer Portal and click on ‘Services’. From here, add the ‘HTTP REST API’ to your Active Services. Then, click on ‘Manage’, which will take you to a new page, where you will see your service username and API token.
  
  Don’t have an account with us? Click on the button above to get started today!

• SMPP API - How to send your first message

  To send messages via the SMPP protocol, a bind to our SMS gateways needs to be established. This can be done using open source software, such as Kannel (kannel.org). Once the software is set up and ready to use, a transmitter or transceiver bind to our gateways must be established using the following SMPP parameters:
  
  system_id – identifies the user requesting to bind (username)
  
  password – password to allow access
  
  interface_version – indicates SMPP version supported by user
  
  address_range – the user address
  
  Once a bind is established and kept alive, messages can be transmitted. Delivery reports will be returned to the same system_id as the messages were submitted from.
  
  All you need to get started is your service username and password, which you can achieve in just a few clicks. Simply log into the Sinch Customer Portal and click on ‘APis’. From here, add the ‘SMPP API’ to your Active Services. Then, click on ‘Manage’, which will take you to a new page, where you will see your service username and password.

• Why is low SMS latency important?

  Some SMS messages need to be delivered immediately to be of any use, so low latency is particularly important here. Use cases like 2 factor authentication, banking or ticketing applications are good examples of SMS messages where an instant delivery is important to the end user - they may well need to take action as a result of receiving the SMS message, chances are they're probably waiting for it to arrive - so speed is of the essence. If a customer doesn't get their expected SMS within a time frame they feel is acceptable (usually around 11 seconds), they'll most likely request another message which results in a higher cost for your business in the long run.
  
  Low SMS latency results in lower cost and higher customer satisfaction - by connecting directly to the carrier network Sinch bypass needless delays that naturally occur as you transit other networks.