How IOS is forced to implement social media: Sina Weibo API

ContentsMark: UseUser Authentication and text sharing.

Sina's documents are well written and clear and easy to find.

 

In terms of API authentication specifications, basic authentication has been canceled, Oathu2.0 Internal Testing, not yet open, OnlyOauth1.0 .

For Oauth1.0 Of Implementation Sina is fully compliant Standard Specification Come, there's no self-defined, like kaixin.com.Yi Parameters.

 

Oauth1.0Three points must be noted in the authentication Implementation Details:

1. Exercise caution when using third-party sdks hanging on the official website, especially when you do not need to implement a complete Weibo client.

2. on the web page where the PIN is displayed, there will be 6 digits. You can directly parse HTML to get the pin. During the warranty period, you can take the third step to obtain the access token. If the token fails, enter it manually. Prevent Sina from changing the pin format in the future, for example, converting it to the image.

3. Sina supports two authentication modes: header and query string. We recommend using the header mode. In my personal opinion, if you want to implement a common SDK for multiple social media, the header mode is also the best choice (only the header mode is supported for Douban ).

 

There is nothing to say about API calls. Pay attention to the call frequency. Refer to this:

Http://open.weibo.com/wiki/Rate-limiting