Send sms api
Send sms api code#
REST API Transactional SMS API - Use this REST API and OAuth credentials to send SMS to contacts already opted-in to an SMS program using RECIPIENT_ID, Mobile number or other lookup key values.
REST API to send SMS to contact source: Send an SMS message to an Acoustic Campaign contact source that is published, with the ability to pass in a message name.
Get published messages: Get a list of published SMS/push notifications along with given attributes to use for further consumption. Integrating our developer-friendly global SMS API into your communications platform is simple and makes sending SMS text messages to your customers fast and.
Go to the REST API methods topic to get a complete list of REST APIs, some of which can be used for SMS messages. See the Test your SMS API Call section at the bottom of the Get SMS programs REST API article. Click here for a complete updated URL list. Paste the following URL in your browser.Ī, where x is your pod number. Transactional SMS external consent REST API Use transactional SMS messages to input contacts having SMS consent managed outside Acoustic Campaign All we need to do is send a POST request to the API with API key, sender ID, phone number and the message body. Send transactional SMS messages to input contacts having SMS consent managed in Acoustic Campaign The service provider that I’m using has a REST API. Get published messages from Acoustic Campaign Use the gateway API to send SMS messages from an external systemĮxport messages from the SMS Campaign Manager
Send sms api code#
And, while iOS has no high-level API for sending email, the various email protocols are publicly documented, so you can implement your own sending code (or adopt some third-party library for this).Before using SMS APIs, get SMS API credentials and learn about the common SMS API use cases listed below. I presume that your users will have email set up on their devices, so that solves that side of things. With regards SMS, iOS has no APIs for sending SMS without user interaction (see QA1944 Sending SMS Programmatically). For example, if your iPhone users only use iMessage, there’s no way for you to message them because there’s no way to send iMessages programmatically (and the protocol is not documented for third-party developers, so you can’t implement your own client). If so, you should talk to the folks running that service to see if you can send messages that way. This API is connected to our Contacts feature, meaning that you can send an existing contactId in. Does your organisation require that all users subscribe to some organisation-wide messaging service. This Send SMS API sends a single message to a contact. With regards other messaging protocols, the challenges relate to the devices to be notified. That is, you set up a server with the ability to send SMS messages and then have your clients connect to that server and ask it to send an SMS message on their behalf. So if you choose SMS, you’ll have to implement your own SMS gateway. With regards SMS, iOS has no APIs for sending SMS without user interaction (see QA1944 Sending SMS Programmatically). So the choice isn’t between SMS and Wi-Fi, it’s between SMS and some other messaging protocol. Then, on top of TCP, there are a variety of messaging protocols, email, iMessage, and so on. Most Wi-Fi networks carry TCP/IP, with TCP being a transport protocol. OK, let’s nail down some terminology first.
