Twitter API usage rule has been changed and the number of requests is within 60 basic / hour

Many people who use Twitter think that they are using tweets from third parties rather than tweeting them directly from the browser, but use of the Twitter API used in such applications The rules will change. Because it is quite a big change, not only the developer, but the influence on the user seems to be big.

Changes coming in Version 1.1 of the Twitter API | Twitter Developers


Twitter Blog: About change of API usage rule in Twitter API v1.1


Although the version of Twitter API is currently "1.0", version 1.1 will be offered within a few weeks, and the major changes between 1.0 and 1.1 are as follows.

· Approval of all API endpoints
· Adopted rate limiting method for each endpoint
· Scheduling future developers rules, especially related to Twitter clients

First, in Twitter API v1.0 it is available without approval up to a certain endpoint. Since Twitter only recognizes the IP address of the application, the ratio of using API for bot and scraping (data extraction) is very high. Since the authentication process was added to prevent such malicious use, API v1.1Approval required for every access.

AlreadyOAuth, The authentication token used in API v1.0 is transferred to API v1.1 as it is. If you are using the Twitter API without using OAuth, you need to update your application to use OAuth by March 2013. The transition period from API v1.0 to API v1.1 is 6 months since API v1.1 was released.

Next, in API v1.0, the limit on the number of requests was 350 times per hour, irrespective of what information the request is about. However, in this uniform way, to prevent the abuse of Twitter resources, access provision for necessary request was restricted. Therefore, basically in API v1.1Number of requests 60 times per hourAs for the API which requires a lot of access such as tweet display, profile display, user search etc. on that, separately720 times 1 hourIt will be changed to the form that it provides it. According to Twitter, most APIs are said to be no problem with this rule "up to 60 times per hour", detailed document will be issued at the same time as API v1.1 release.

And finally, about changing developer rules.

So far"Display guideline (guideline)" is changed to "display requirement (necessary condition)"It will be. In other words, if you provide a service that makes tweets appear somewhere, you can display a link from your user name ("@ gigazine" in GIGAZINE) to your profile, display the appropriate tweets action (RT, reply, favorites) , It is indispensable to display tweets according to each device. When tweets are displayed in a manner not meeting this display requirement, it is possible that the application key is invalidated, that is, the access permission to the Twitter API may be canceled.

In addition, if you pre-install client applications on terminals such as mobile phones and smart phones, SIM cards, chipsets, etc., approval by Twitter is required. This is from the idea that Twitter wants to confirm that the developer provides the "best Twitter experience" to the user, and if you preinstall without approval, you may invalidate the application key.

And about user token. Developers need to negotiate directly with Twitter if the application uses a large number of tokens of 1 million or more, that is, the number of users exceeds 1 million. This seems to be because Twitter noticed the trend of increasing API usage over the last few years and realized that something could be done for the user's interests, the developer's business.

Apart from this, if you are developing a Twitter client that needs access to timelines, settings, DM, etc., it is said that you need to contact Twitter when the number of users reaches 100,000 about. If you are already over 100,000 people, 200% of tokens will be issued as of today's number of users, but if it is also full, Twitter's permission is required.