Word came overnight from Twitter’s Developer Platform that things are going to get unpleasant, and potentially expensive, for applications and websites which depend on Twitter APIs.
For years, free access to those APIs has made it possible to reproduce tweets, timelines, and the like with fairly simple code. As a result, untold millions of people who might otherwise have missed this content were exposed to it, presumably enhancing Twitter’s popularity and, thus, more than compensating for whatever it might have cost Twitter to provide the APIs.
Well, boy, howdy: the loan-burdened Twitter couldn’t very well have that, could it? So, now, free access to those APIs is going away.
A tweet thread issued overnight (U.S. time) from the @TwitterDev account made the disclosure:
Starting February 9, we will no longer support free access to the Twitter API, both v2 and v1.1. A paid basic tier will be available instead 🧵
6:05 AM • February 2, 2023 (UTC)
Over the years, hundreds of millions of people have sent over a trillion Tweets, with billions more every week.
6:06 AM • February 2, 2023 (UTC)
Twitter data are among the world’s most powerful data sets. We’re committed to enabling fast & comprehensive access so you can continue to build with us.
We’ll be back with more details on what you can expect next week.
6:07 AM • February 2, 2023 (UTC)
Never mind the fact that one week is an incredibly short window for app developers and websites to decide whether they are willing to pay for access to the APIs, especially given that the pricing is yet to be disclosed. Consider that those which can’t pay are going to be hampered tremendously. As Jess Weatherbed put it in her related article for The Verge:
Many small developers have used Twitter’s free API access to create fun tools and useful bots like novelty weather trackers and black-and-white image colorizers which are not intended to earn income or turn a profit. As a result, it’s likely that many bots and tools utilizing Twitter’s free API access will need to charge a fee or be shut down. It would also impact third parties like students and scientists who use the platform to study online behavior and gather information for research papers.
I suggest you read both that article and Ashley Belanger’s Ars Technica article for more details about Twitter’s decision and the ramifications thereof.
For my part, this all means that, if I hadn’t already deprecated my multiple posts from last year about using the Twitter APIs to embed tweets fully statically, this would’ve killed them for sure.
Effects on Hugo-based sites
By the way: if you’re a Hugo user who employs its built-in
tweet shortcode, this doesn’t appear — so far — to affect Twitter’s oEmbed API, on which that shortcode depends. The same API also enables many of the embedded tweets you see on the web, so making a similar change to that API could cause a massive amount of content to go away almost instantaneously. It would be a “nuclear option” kind of event.
If you still use
tweet, just be sure you make the appropriate privacy settings. For example, here’s how Hugo, with those settings, renders that initial tweet about the change in the affected APIs’ availability:
Starting February 9, we will no longer support free access to the Twitter API, both v2 and v1.1. A paid basic tier will be available instead 🧵— Twitter Dev (@TwitterDev) February 2, 2023
. . . or, at least, that’s how Hugo renders it unless and until Twitter kills free access to that API, too. Use it, and Twitter in general, at your own risk.