Last Autumn Twitter announced that it planned to roll out some changes to how it communicates with third party feeds, systems and apps. Essentially the changes aim to deliver a more authentic and consistent user experience across Twitter, whilst introducing firmer guidelines around the use of the Twitter API.
The new system is called a REST API. An API is a set of computerised instructions, guidelines and standards that let you connect to a web based application.
There are 2 main changes to note for websites:
- Twitter want you to authenticate through them for every API end point, meaning that to display a Twitter feed you must be signed in to the application. This will hopefully prevent the malicious use of the API and enhance Twitter’s understanding of how it is being used.
- Individual API end points will be rate limited at 60 requests per hour. This means that your site can only be fed data from Twitter 60 times every hour. This might sound a bit severe, but the idea is that it takes the load off Twitter’s servers to provide users with a wholly better, faster and more reliable service.
What to do next
Install a new Twitter feed on your site that connects through the API. After Digital has built a solution that works to the new parameters. If you’re interested in having your Twitter feed updated get in touch with us and we can look at your specific requirements.
Once you’ve implemented your new Twitter feed make sure that it has a caching option and that this is turned on. This will allow your site to remember the data Twitter sends it and it won’t need to keep jumping back to get more, meaning that you should easily operate within the new limits.