Changes to the TWiT API: What App Developers Need to Know

If you’ve built a TWiT app, or you’ve been thinking about it, the TWiT API has changed in ways that make it easier to use. It’s now open to everyone, it lives at a new address, and the documentation has moved. The data and the calls you make to get it are the same.

We’re leaving 3scale

Access to the TWiT API has been managed through 3scale. Red Hat has decided to retire the 3scale API Management product on June 30, 2027, and support and access will end on that date. Because our API depended on it, we’ve set up a new API host that doesn’t, well ahead of the deadline.

New and improved documentation

Oracle has also ended Apiary Cloud Service, with an End-of-Life date of October 31, 2026, and is likely to delete our API documentation hosted there any day now. As a result, the API documentation has moved from Apiary to apidocs.twit.tv. Besides the reference for every endpoint, it includes a downloadable OpenAPI specification you can use with your own tools. It also lists each endpoint’s page size and cache lifetime, and the available filter, sort and paging parameters.

Use api.twit.tv

In order to keep the existing 3scale API running during this transition, we put the new API host at a different URL. Point your API code at api.twit.tv instead of twit.tv. The endpoints and responses are the same, so for most apps this means changing the host in your base URL:

• Old: https://twit.tv/api/v1.0/
• New: https://api.twit.tv/api/v1.0/

We’re keeping the old address running for as long as we can, so existing apps will keep working for now. But the old setup depends on 3scale, so any app still pointed at the old API when 3scale shuts down on June 30, 2027 will stop working. Please update before then.

No account, no keys

You no longer need a 3scale account, an approval, or an application ID and key. The API is open to everyone, and every endpoint is read-only. A plain GET request works:

curl "https://api.twit.tv/api/v1.0/shows"

If your app sends an access-token header or app-id and app-key headers, you can remove them.

What hasn’t changed

The API itself is unchanged. You make the same calls and get the same JSON responses, with the same filters and sorting, at the new address. Our Developer Guidelines are also unchanged. They still ask, for example, that you not call your app "TWiT", keep your app free, and please do not do weird things to our logo.

Please be a good API citizen

The API is open, so please treat it kindly. We still recommend caching responses rather than hitting the API every time a user wants something like an episode list because your cache will always be faster than API requests.

Questions and showing off

Email api@twit.tv with questions, and tell us when you want to show off something cool!