I want to use the SurveyMonkey API to trigger a SM collector to send an email directly after one of our technicians has completed his work. To this effect I am using the create_recipients API method. To send a custom message I need to provide the email_message_id. I cannot find this id. When I leave out the id SM sends the default message which is in english (I need dutch). Can anyone tell me where to find this id?
I contacted the Surveymonkey Support desk; they told me that the "email_message_id" will be visible if you use the "Send_Flow" API-call. It appears that the message_id is not otherwise (easily) obtainable.
UPDATE -- 3/3/2016
Have now, in fact, created a flow in which the resulting JSON returns the e-mail message. So the way to go is to use 'send-flow' in combination with 'create_recipients'.
With many thanks to Alfred from Surveymonkey Support.
The v2 API has no way to retrieve the email_message_id of a collector. That will be possible in v3 which should be available soon. Until then it is still possible to find the email_message_id in the HTML. Here's how to find that ID in the code for the collector, via chrome's developer tools:
Go into the Email Collector
Find the message under "Message History"
Right-click on the row and select "Inspect" (Assuming you're using Chrome)
You'll see something to the effect of <li id="27713004"> (The ID will be unique to your message)
Related
I want to export everyone who has reply stop (opt out) for my messages. I see that my options are
API. However, through the API I can see that I get everything in pages of 50 messages, so I have to go and do a lot of code to go page by page, message by message just to check if the content is stop. Seems a bit unnecessary for a 1 time job.
From the console in my account, however when each time i try to filter on status received I get the following error, and when I dont filter I get error:
Your export request has more than 10,000 records, please filter your results and try again.
Surely there must be an easy way that I can get all the list of numbers that had opt out?
This answer above is not strictly true as of October 2020. Twilio now has an "insights" dashboard that allows you to view and download "Opt outs Received". When you click on that dashboard you are able to see and download the information.
It is under: Programmable Messaging -> Monitor -> Insights
Our account has "Opt-Out Management" enabled and this addition has been a game changer in finding out what users have or have not done in our system.
There isn't a way to export all opt-outs for LC's/TF's that Twilio maintains on your behalf but opt-outs are forwarded to your application for logging as well as added to the Twilio maintained opt-out list. Your application can keep track of the opt-outs this way. You can find more details in the Help Center article below.
Twilio support for opt-out keywords (SMS STOP filtering)
"When Twilio receives one of these replies, we will create a "blacklist" entry on our side, and then pass the message on to your webhook. Once we have a blacklist entry for a particular recipient phone number, any future attempts to message them will be met with a 400 response from our API, along with Error Code 21610 - Message cannot be sent to the 'To' number because the customer has replied with STOP. Recipients can disable this message stop, and resume receiving messages with the START, YES, or UNSTOP commands as outlined below."
Also, if you use the Twilio helper library for the respective language, it handles the paging for you, for example, for Node.js, reference.
Usage and Migration Guide for Twilio's Node.js Helper Library 3.x
"One of the biggest advantages of twilio-node 3.x is that it automatically handles paging for you! In both list and each, you can specify the maximum number of instances to grab (limit), and the page size (pageSize). The library will take care of everything else."
How can I update mail to show a "warning" message that exists on a users' mailbox as like what you see when mail is moved to the "junk mail" folder using the Graph API? See attached screenshot. Obviously, I want this message to be customised with my own text. It's not possible to update messages if they aren't draft (isDraft=false).
I dont think that Transport rules are good for us because I want to add that label after the message has arrived into the users' mailbox.
I know that its possible to add Custom Attributes to a message resource - https://learn.microsoft.com/en-us/graph/api/resources/opentypeextension?view=graph-rest-1.0
Can I utilize it? any way that you can recommend to do such a thing?
Do I need to develop any addon for that?
After speaking to the PM , there is no supported scenario to do this. If you require this feature you can make a request on https://microsoftgraph.uservoice.com/
Our customer wants to see a report of all their current users' last login dates, but I couldn't find a way to get that information from the current API:
http://docs.valence.desire2learn.com/res/user.html
It's a little frustrating, because it's so easy to get this data in the UI itself:
Is there any way we can get that data through the API? Thanks!
Currently, there is no way to get this information via an API call; however, you are not the first person to inquire about this, and I suspect it's on D2L's list of improvement items for their developer platform.
We use EventBrite for managing some free events: works great.
We also make extensive use of the waitlist feature.
I would like to script the synchronisation of the EventBrite ticket list contacts (sold and waitlist) with another system.
(yes, I know, I can manage contacts in EventBrite. But we have an existing system and I want to keep using that)
There does not appear to be an obvious way to retrieve any information about people on the waitlist via the API? Is this possible?
Each of the available API access methods are listed here:
http://developer.eventbrite.com/doc/#methods
Waitlists are not currently available.
This should do the trick. Run it in your web browser to see an xml list of all attendees:
https://www.eventbrite.com/xml/event_list_attendees?id=123456&app_key=your_app_key
You'll have to signup for a developer's key to run the query though: https://www.eventbrite.com/api/key/
The down and dirty method to get the eventID to make sure it's working is to view the page source of your EventBrite page, and search for "eventID" or "eid".
You can get the event id through the EventBrite API as well: http://developer.eventbrite.com/doc/events/
Twitter's REST API returns a in_reply_to_status_id value for tweet statuses, yet the Search API does not.
What puzzles me is, if you search using the http://search.twitter.com/ webpage directly, tweets that are in reply to another tweet contain a "Show Conversation" link, but when searching using the API directly, there doesn't seem to be any data suggesting that a conversation exists (with JSON, at least).
How does this search page know which tweets are part of a conversation, and what would be the best way to emulate this behaviour (JSON preferred) in a rate-friendly way? I imagine I would have to do additional calls or something...?
related_results is officially dead along with the v1 API. It appears official Twitter apps use a call to /1.1/conversation/show.json?id=___ as mentioned here https://dev.twitter.com/discussions/17647 however it appears to be blocked from non-Twitter clients.
Just check the JSON field "to_user", which contains screen_name of the #replied person. If its null, you can assume its not a reply. You could also check, if the tweet string starts with a #username, which
http://search.twitter.com/search.json?q=%40aplusk
When you use the search.twitter.com, look for a field name in_reply_to_status_id This contains the original status_id to which this tweet was a reply. Next, there is a currently unsupported/undocument api call to get the whole conversation:
https://api.twitter.com/1/related_results/show/169145505824256000.json?include_entities=1
The value (169145505824256000) is the status_id you want to retrieve the conversation for.
An update on this as I was just faced with the same problem. The Twitter v1.1 API should now return valid in_reply_to_status_id values. But the unsupported v1 related_results has now gone forever.
You can see information about this, and some suggestions about using the streaming API, at https://dev.twitter.com/discussions/11292