I am setting up a computer system app which will send SMS alert. One can select:
Service type: HTTP, SMTP or SMPP. I've been told to use HTTP.
HTTP(S) Method: Post or Get. I've been told to use Get.
HTTP(S) URL: I believe that https://api.twilio.com/2010-04-01 is correct
HTTP(S) Parameters: gives an example:
username=xxx&password=xxxx&mobNo=%xxxx%&message=%[message]%
I am told that the "%" entries are just part of the mobNo and the message and are not to be entered separately.
I've been using:
username=[my Twilio logon email address]&password=[my Twilio pasword]&mobNo=[myTwiliomobNo]&message=testMessage
I get an error when I send a test message with this that says:
"HTTP(S) parameters filed must contain %mobNo% and %message% for Mobile Number and Message fields"
So, something must be wrong and I suspect the HTTPS parameters as there seems to be nothing else in question.
What should it be?
After much back and forth with folks at Twilio and EventLog Analyzer, it's been determined that the two are incompatible. EventLog Analyzer has a "canned" / programmed interface to the SMS provider and Twilio can't accept the outputs.
I rather get the idea that the SMS market is aimed at web programmers and not users.
Related
I am working on a project in Twilio and Podio, where I am using this code from Podio using POST
POST IN PODIO
FROM URL: https://[(Ref Setting) Setting Value 1]:[(Ref Setting) Setting Value 2]#api.twilio.com/2010-04-01/Accounts/[(Ref Setting) Setting Value 1]/Messages.json
POST PARMS: To=[(Ref Lead) Mobile Phone]&MessagingServiceSid=[(Ref Setting) Setting Value 3]&Body=[(Variable) strMessages]
---This works fine, and I can send my message no problem, I am using a MessagingServiceSid because my volume has increased I have about 4 numbers in the messaging service.
The problem I am encountering is I had a Twilio Studio Flow set up to handle the incoming text messages when I was just sending from the sid, and I am wanting to figure how if I can make sure that when someone responds to my messages they get sent to the studio flow set up to handle the responses. I am also wanting to get the responses back into Podio.
I have tried changing the Numbers settings in messages settings to that particular studio flow, but when I do that, it takes the number out of the Messaging service that I am using to send the messages.
You need to assign numbers and studio flow to a messaging service.
To assign a number to messaging service:
While configuring a phone number you need to go to its "messaging" section and configure with the messaging service.
To connect messaging service and studio:
1) Goto studio flow -> click on the trigger -> copy the webhook URL
2) Goto messaging service -> inbound setting -> paste the URL in request URL
To get the response back to your servers(I am not familiar with Podio), add an HTTP request block in your studio flow. In that add a request URL pointing towards your server and in the request body you can add the body of text which looks something like FROM:{{trigger.message.From}} BODY:{{trigger.message.Body}}
I tried to follow Abhijeets answer, but unfortunately due to the way messaging services and Twilio phone numbers differ, it's not possible to have the SMS replies work correctly.
I tried to do something similar to you. I was triggering the Flow execution by POSTing to the REST API url trigger, and I used the "Send & wait for reply" widget to send and receive a reply from a number. It worked perfectly when only sending from one phone number, but when I switched the "Send & wait for reply" widget to use a messaging service to send it instead, the responses always triggered the "Incoming Message" start of the Twilio Flow. So it made an entirely new execution, and my previous execution never was completed.
After reading a lot of documentation I could never get around this, so what I did was instead just purchase and assign additional phone numbers to the Twilio flow. In my application, I triggered the Flow execution using these phone numbers (randomly), and then the "Send & wait for reply" widget used this phone number to send out the text message. That ended up working for me, since I was only using messaging services to send out SMS messages with multiple different phone numbers.
Trying to set up SMS gateway inside of GPSWOX program and it's asking for the Clickatell url - I used the "Curl" url and placed in the box.
However, when I tried to test the sms it didn't send me anything. Does anyone know if this format is correct?
Thanks
The format is nearly correct. You should use:
https://platform.clickatell.com/messages/http/send?apiKey=******&to=%NUMBER%&content=%MESSAGE%
You can test it by pasting the example url in your browser (with NUMBER and MESSAGE replaced of course)
I want to use Twilio to create an SMS relaying service where the Twilio number is the only number that is exposed, much like web proxy servers that allow you to access the Internet anonymously. I've used the example php code that twilio provides, saved it to a php file and hosted it on a public web server, then updated the messages URL on the Twilio site accordingly. Any message sent to the Twilio number the is forwarded to my mobile. Everything works fine, except for the fact that when I reply to the forwarded message from my phone, the reply includes a header that says "Sent from your Twilio trial account - + mymobilenumber" I understand that the header is inserted because I have a trial account, however I don't want the mymobilenumber field to be exposed. Is it possible to hide this?
I should mention I'm not really a programmer but I'm learning with Twilio.
I followed the example given here:
https://www.twilio.com/help/faq/sms/how-do-i-forward-my-sms-messages-to-another-phone-number
Thx
Antonio
A short code is a 5 or 6-digit number that can send and receive messages with mobile phones. These high-throughput numbers are perfect for apps that need to send messages to lots of users or need to send time sensitive messages. You can buy shortcodes from Twilio or port existing short codes to our platform.
I would like to send a text message survey (eg. "How happy were you with X service? Reply 1 for satisified, Reply 2 for not satisfied") to multiple recipients. From the responses, I would like to create a report on the recipients that responded 1 vs the ones that responded 2. What is the best way to do this with the Twilio API? Does my app need to store the results from my incoming SMS message or does Twilio store these so I can query the results? If the former is the case and TwiML is involved, how do I parse the response and store the result? Thanks!
** Disclaimer: Twilio evangelist here **
Chirag:
So it sounds like you have two requirements here:
Use Twilio to send outbound text messages to different recipients
Capture a users reply to that message
For the first requirement, you can start by going to Twilio.com and signing up for a new account. Its free to start and we give you a Twilio phone number you can use to start to build your app. Once you have the Twilio phone number, you can use the REST API to start sending outbound text messages from that Twilio phone number. We have a quickstart that shows you how to do this:
http://www.twilio.com/docs/quickstart/php/sms/sending-via-rest
Note that this link goes to the PHP sample, but you can use the drop down at the top of the page to pick from other stacks like .NET, Java, Python or Ruby.
Once you've sent an outbound message you need to capture the replies to that message (your second requirement). Twilio uses something called a webhook to notify you about incoming SMS messages.
A webhook is basically a URL exposed by your application and associated with your Twilio phone number. You can configure the URL associated with your phone number in the Twilio dashboard.
Each time we receive an incoming SMS message on your Twilio phone number, we will make an HTTP request to that URL. As part of that HTTP request we send along metadata about the inbound message like the phone number that the message was sent from and the Body of the message. The full list of parameters we send is here:
http://www.twilio.com/docs/api/twiml/sms/twilio_request
Now your app can pull those parameters out of the request and do whatever it wants with them. Since we already are sending the body of the message as we receive it, Tims suggestion of tracking the responses based on the From parameter and storing the message body in your own database is a good suggestion.
This quickstart shows receving an incoming text message, grabbing the From parameter and then responding by sending back from TwiML:
http://www.twilio.com/docs/quickstart/php/sms/replying-to-sms-messages
In your case, if you don't want to reply to the incoming message, just omit the TwiML response.
Hope the helps. Lets me know if you need more info.
Devin
Track the responses using the From parameter (and using Body to identify the selection). Yes, Twilio stores those messages, and you could query the API - but it's likely better to just store it in your own database.
I hope this gets a response.
Say Person A sends an SMS to a shortcode in a certain syntax. How could a confirmation SMS be sent to Person A's mobile phone automatically ("Your message has been received successfully!"), after determining that the SMS received from Person A is in the correct syntax? I'm a total newbie when it comes to SMS - so if anyone could describe the entire end-to-end process/architecture that could make this happen, I'd be grateful!
You'd have to find a gateway provider who handles the receiving and the sending of messages for you using a defined API talking to a script/application in the language of your choice.
You usually receive messages on a number defined by the gateway provider. Incoming messages will trigger a call to a URL defined by you. Behind that URL will usually be a script that then performs the desired actions (e.g. parsing the message and sending an automated response SMS through the gateway provider.)
SO questions related to SMS Gateways:
Sending an SMS myself
SMS from web application
BulkSMS provides facilities for you to both send mobile terminating (MT) messages and handle receipt of mobile originating (MO) messages.
You can request a short code, which your users then send MOs to. The message can then be relayed, via a simple HTTP request, to your web server. You application then determines a suitable response and replies via SMS by calling the MT API of BulkSMS.
There may be restrictions and legislation applicable, depending on where you are, where your users are and the networks the messages are passing through. They can provide assistance here too.
International incoming numbers http://www.bulksms.com/int/w/solutions_incoming.htm
Receiving messages via HTTP http://www.bulksms.com/int/docs/eapi/reception/http_push/
Sending API http://www.bulksms.com/int/docs/eapi/
Short codes in South Africa http://bulksms.2way.co.za/w/solutions_psms.htm
Hope this helps