The microblog open interface limits requests to a certain number of times per period of time. The limited unit time is hourly and daily; The restricted dimensions include single authorized user and single IP; Some special interfaces have separate request times limit. For example:

• • A single authorized user within an application can only request the microblog open interface 100 times a day accumulatively;
• • An IP address can only request the microblog open interface 15000 times per hour;
• • The authorized user of microblogging interface can only request 30 times per hour;

When developers cannot call the interface to meet the development needs, and the number of authorized users is more than 200000, developers are welcome to apply for partners to negotiate. On the premise of ensuring user privacy and information security, we will carry out in-depth cooperation based on the principles of cooperation, legality and mutual benefit.

Cooperation application channel: Please open the official account of the platform on Weibo

First, microblogging open interface technology is an HTTP polling protocol in principle, not a real-time push protocol. Therefore, even if the refresh frequency is increased, it is impossible to obtain the latest information immediately. According to experience, we suggest 3-5 minutes/time for updating frequency.

The current frequency limit can meet the demand as long as the user takes the initiative. In addition, considering the actual needs of developers, the frequency will be slightly relaxed so that developers can realize some very creative functions (some complex functions may need to combine data to call multiple interfaces). However, we are opposed to the malicious capture of user data through the server's robot program when the user is not actively triggered, which will easily trigger the frequency limit.

In addition, developers can save their own access frequency more intelligently. For example, if no new data has been obtained from the pulled data in recent times, they can reduce the access frequency appropriately. It is also appropriate to cache some data on the client, rather than directly calling the microblog open interface every time. However, it is important to note that the microblog open platform prohibits third-party servers from storing user data, so developers of this method should note that they can only cache data on the client, not upload it to their own servers.

In addition to the above frequency restrictions, we will also have additional request restrictions for test accounts for applications that fail the review and are under development. Each failed application can only authorize 15 test accounts to request interfaces. Other accounts cannot request interfaces through this application. When an application is approved, the limit is automatically cancelled.

In addition, Weibo attaches great importance to the user's experience of reading the content stream. Therefore, based on not harassing normal users to read the content of Weibo, when the user requests to post Weibo, comments and other written content operations through the test account in the test state, although the request can be successful and the content can be sent normally, only the test account can see the test content, The test content will not be actually distributed to the content stream of non test accounts.

The test account is set in "My app>Edit app properties>Test account" You can find it in.

The microblog open platform has always attached great importance to the protection of user data, so it has been constantly improving its own security mechanism. At present, the security mechanism of microblog open platform can accurately identify whether the interface access is user behavior call or robot program call.

We hope that developers can follow the request restrictions and the developer agreement of the microblog open platform, and based on the user's active behavior normal access interface, rather than calling the interface through robot programs, or non user active behavior, or even capturing a large amount of microblog user data.

Therefore, excessive calls exceeding the frequency limit, or frequent calls by non users' active behavior (even if the frequency limit is not exceeded) to the microblog open interface will lead to your application (appkey) and IP being identified as a robot program by the security mechanism of the microblog open platform, or malicious grabbing of user data, which violates the microblog developer's agreement. As a result, the access permissions of the application and IP interfaces are blocked, and the requests for all open interfaces are restricted.