In this announcement thread, they mention the following
"Over the next 30 days, we will deprecate current access tiers such as Standard (v1.1), Essential (v2), Elevated (v2), and Premium so we recommend that you migrate to the new tiers as soon as possible for a smooth transition."
Source: https://twitter.com/TwitterDev/status/1641222786894135296
Genesys Cloud currently relies on Twitter's v1.1 API. My question is;
a) Is future access to those endpoints being depreciated?
or
b) Are those endpoints being depreciated entirely?
What action(s) must be taken for existing clients using the Twitter integration, and if Twitter will be deploying a new API, what's Genesys' ETA on updating the existing integration to use it?
@SamStevens great question, unfortunately i can't provide much of a helpful response at this time though. As you are already aware, I'm sure, Twitter has been aggressively announcing API changes with very little lead times. We will continue to monitor any changes that could affect our Genesys Cloud Twitter messaging integrations as best we can, but the situation is constantly evolving.
In the past, Twitter DM APIs were not a heavily regulated part of the Twitter Developer App, and it's unclear if these recent announcements change that directly or not.
We will continue to keep a close eye on any formal documentation Twitter supplies, that will help understand their changes more closely.
Thanks for your response, I understand the situation is outside of Genesys' control. I just wanted to make a post to make sure that it's being monitored or if someone had more info to share.