Update as of December 6th, 2021:
We plan to extend the retirement of the endpoint beyond November 23rd. This move will hopefully allow a very small number of developers to make a smoother transition away from this deprecated endpoint towards the supported publish.twitter.com/oembed endpoint. Once we have a new retirement date, we’ll update this forum post. In the meantime, please let us know if you have any questions on our forums.
The Twitter Developer Platform has allowed the embedding of Tweets and timelines into a variety of websites for a long time.
Along with publish.twitter.com, which was introduced in 2015, there’s also an oEmbed endpoint which makes it easier for developers and third-party plugins to insert embedded Tweets and timelines into their own integrations.
The api.twitter.com/1.1/oembed endpoint which was released in 2011 was deprecated in 2015, although it wasn’t fully retired at that time. We’ve encouraged developers to use the publish.twitter.com/oembed endpoint instead, which is the same and has no appreciable difference.
Today, we’re sharing that the api.twitter.com/1.1/oembed endpoint will be retired and removed on November 23, 2021, so that new features can be supported in a consistent manner.
If you are using the v1.1 version of the Twitter oEmbed endpoint, you should move your integrations to target publish.twitter.com/oembed, which has similar functionality. You can learn more about the oEmbed API endpoint in our developer documentation.
After November 23, 2021, the only official and supported API endpoint for Twitter oEmbeds (embedded Tweets and timelines) will be via publish.twitter.com/oembed. The api.twitter.com/1.1/oembed path will no longer be available. We encourage you to migrate as soon as you can.
Deprecated endpoint: api.twitter.com/1.1/oembed
Current and supported endpoint: publish.twitter.com/oembed
If you have any questions, please use our Twitter for Websites category here on the developer forums.