Several times this year, and most recently earlier this month, I’ve written about how to embed fully static tweets in one’s website, so as to include Twitter content without Twitter tracking scripts. I originally found that doing this by accessing Twitter’s preferred “v2” API was impaired by one particular shortcoming identified in the appropriate documentation:
Note that video URLs are not currently available, only static images.
Since then, I’ve periodically checked that documentation to see whether this situation had improved. Lo and behold, this weekend, another such check revealed this text was gone. Although Twitter apparently didn’t announce the shift in its Developer Platform changelog, my testing showed that, as I’d hoped the documentation change was indicating, the v2 API now does provide URLs for videos. Thus, I am now working on a method to use the v2 API to produce static tweet embeds with videos, while also working with the oEmbed API to provide superior text. Will provide corresponding code ASAP.
Update, 2022-08-21: Turns out that effort wouldn’t be worth it; you still end up having to use other APIs to pull in what Twitter calls the “Summary Card with Large Image” which one typically sees in a tweet that includes a URL to a suitably managed web page.
In short . . . never mind. I’ll stick with what I’ve got now. The v2 API may be what Twitter wants everyone to use, but it’s both a major pain in the ass and not sufficient for proper embeds. To be fair, I know that’s not what Twitter wants us to do with the v2 API. (On the other hand: after spending hour after hour staring at the v2 API’s dev-unfriendly output and trying to find stuff in it, I’m fairly sure what I’d like Twitter to do with the v2 API.)