The Twitter Direct Message API allows developers to create engaging customer service, marketing, and engagement experiences. Developers can send and receive direct messages, create welcome messages, attach media to messages, prompt users for structured replies, link to websites with buttons, manage conversations across multiple applications, display a custom image and name in a direct message, and prompt users for NPS and CSAT feedback.
Despite the recent privacy snafus from some social media platforms, developers are just as interested in creating social applications as they ever were. Here we take a look at some the social APIs in ProgrammableWeb's directory that get the most traffic, and what developers can do with them.
This segment of the past year's APIs focuses on eCommerce, Marketing and Social Media. Sub categories covered here include Advertising, Content, Printing, Products, Catalogs, Subscription, Taxes, Feedback, Auctions, Shipping, Ratings, Personalization, SEO, Engagement and others.
With no prior warning, Twitter has changed how apps can access images sent through Twitter's Direct Message API. Twitter was unable to give prior notice for security purposes, but the changes are in effect. Twitter encourages developers who access images through the API to check their integration.
Twitter has announced that it is delaying the shutdown of legacy APIs as its new Account Activity API is now generally available to all developers. The legacy APIs, namely the Site Streams and User Streams APIs, as well as Direct Message endpoints, were slated to be turned off on June 19.
Eight APIs have been added to the ProgrammableWeb directory in categories including Engagement, Database, and Emergency. Highlights include the Xillio API for connecting applications to content repositories such as Dropbox, Hadoop, Zendesk, Github, and many others. Here's a look at what's new.