I got this email from Twitter today… Does anyone know what needs to be done in order for Zammad to continue to use Twitter messages from customers?
We'd like to remind you of some important and imminent changes to the Twitter API platform to ensure you understand what is happening. The following endpoints are set to be sunset and will be turned off on August 16th, 2018.
• User Streams
• Site Streams
• GET direct_messages
• GET direct_messages/sent
• GET direct_messages/show
• POST direct_messages/new
• POST direct_messages/destroy
On and after this date, new connections to User Streams and Site Streams (including control endpoints) will no longer be accepted, and requests to the legacy DM endpoints will return errors.
We have new endpoints and services available that provide similar access and, for Direct Messages, some additional functionality:
• Account Activity API enterprise and premium
• GET direct_messages/events/list
• GET direct_messages/events/show
• POST direct_messages/events/new
• POST direct_messages/events/destroy
We have two migration guides to help with this transition, and we encourage you to start this migration as soon as possible:
• Account Activity API Account Activity API migration guide for those going from User Streams and Site Streams to our new webhooks based service
• Direct Message migration guide for those migrating between Direct Message REST endpoints
Hi @bruce78 - just to give you a heads up: There are some manual steps to be performed in the Twitter App-Administration views. How to handle those is the only thing blocking us from releasing the changes. We will decide tomorrow how we will approach it and will release the changes afterwards. I’ll post a link here.
Hi @bruce78 sadly we didn’t make it in time We’re currently waiting for Twitter to approve one of your accounts as a Dev account so we can proceed with the final QA, documentation etc. However, if you want to speed your migration phase up apply for a Twitter Dev account - which is now mandatory
We’re currently waiting for Twitter to approve one of your accounts as a Dev account so we can proceed with the final QA, documentation etc. However, if you want to speed your migration phase up apply for a Twitter Dev account - which is now mandatory
@thorsteneckel I’m assuming that you have attempted to create a new app to test the new API stuff and got caught up in the need to have a new Twitter Dev account as below?