Weibo open interface limits only requests per period of time A certain number of times. The unit time limit includes hourly and daily; the limit dimension includes single authorized user and single IP; some special interfaces have separate request limit. For example:

• • An in-app authorized user can only request the Weibo open interface n times per hour;
• • An in-app authorized user can only request Weibo cumulatively every day Open interface m times;
• • An IP address can only request the Weibo open interface x times per hour;
• • Authorized users who post Weibo interface orders can only request y times per hour;

Among them, the specific values ​​​​of n, m, x, y, Weibo open platform will adopt the application quality evaluation system to realize intelligent evaluation of application quality. High-quality applications will have higher corresponding values. , that is, the request limit is small. Therefore, the limit value is not fixed, and different applications have different limits, depending on the quality of the application itself.

When the interface called by the developer cannot meet the development needs and the number of authorized users exceeds 200,000, the developer is welcome to apply for partnership negotiation. Under the premise of ensuring user privacy and information security, we will conduct in-depth cooperation based on the principles of cooperation, legality, and mutual benefit.

Partner application channel: weibo_app@vip.sina.com

First of all, the technical principle of Weibo’s open interface is HTTP polling ( polling) protocol, not a realtime push protocol. Therefore, even if the refresh frequency is increased, the effect of obtaining the latest information immediately cannot be fully achieved. Based on experience, we recommend that the update frequency is 3-5 minutes/time.

The current frequency limit can meet the needs as long as the user takes the initiative. And considering the actual needs of developers, the frequency will be slightly looser so that developers can implement some very creative functions (some complex functions may require combining data to call multiple interfaces). However, we object to maliciously grabbing user data through server robots without the user's initiative. This situation will easily trigger the frequency limit.

In addition, developers can save their access frequency more intelligently. For example, if no new data has been obtained in recent data pulls, the access frequency can be appropriately reduced. You can also cache some data on the client side instead of directly calling the Weibo open interface every time. However, it should be noted that the Weibo open platform prohibits third-party servers from storing user data, so developers of this method need to pay attention to only It can be cached on the client, but cannot be uploaded to your own server.

For those that have not passed the review and are under development Application, in addition to the above frequency limits, we will also have additional request limits for test accounts. Each application that fails the review can only authorize 15 test accounts to request the interface. Other accounts cannot request the interface through this application. When the application passes the review, this restriction is automatically lifted.

In addition, Weibo attaches great importance to the user experience of reading content flow. Therefore, in order not to harass normal users to read Weibo content, the test account is used to request Weibo posts, comments, etc. in the test state. During the operation, although the request can be successful and the content can be sent normally, only the test account can see the test content, and the test content will not be actually distributed to the content stream of non-test accounts.

The test account settings can be found in "My Application>Edit Application Properties>Test Account".

Weibo open platform has always attached great importance to the protection of user data. Therefore, it has been continuously improving its own security mechanism. The current security mechanism of the Weibo open platform can very accurately identify whether the interface access is a user behavior call or a robot program call.

We hope that developers can follow request restrictions and the developer agreement of the Weibo open platform, and use normal access interfaces based on user active behaviors, rather than calling interfaces through robot programs or non-user active behaviors. , and even crawled a large amount of Weibo user data.

Therefore, excessive calls that exceed the frequency limit, or frequent calls by non-user active behaviors (even if the frequency limit is not exceeded) Weibo open interface will cause your application (appkey) and IP to be blocked by Weibo The security mechanism of the open platform identifies violations of the Weibo Developer Agreement such as robot programs or malicious grabbing of user data. As a result, the interface access rights of the application and IP are blocked, and all requests for open interfaces will be restricted.