Audit Guide

Thank you very much for reading this document, which shows that you probably have great ideas and applications that will be available to a large number of users on the microblog open platform, and even have been online. We are also happy for this. Thank you for your valuable talent and time to develop Weibo open platform applications. From the perspective of career and remuneration, this has always been a worthwhile undertaking for thousands of developers. We hope to help you join this successful organization. Through it, we hope to help you solve problems encountered in developing applications, so that you can speed up the approval process when submitting applications.

The applications we mentioned here refer to the applications and authorized websites that provide services accessed on the microblog open platform. We have more than 300000 applications in our platform. But we still welcome those high-quality applications to access our platform. However, if your application has no useful use or continuous entertainment function, it may not be accepted by us. If your application looks like a product that only took a few days to piece together, or just wants to catch your friend's eye in our platform, please be prepared for rejection in advance. We have many developers with rigorous attitude who do not want their high-quality applications to be filled with some amateur works.

As a developer, what kind of applications are you most concerned about? This document cannot answer this question, but it will help you understand what applications can be published on the microblog open platform.

After your application development is completed and relevant resources are packaged, you need to submit it to the microblog open platform for application review. After the review is passed, the application will go online and be found by microblog users.

If the application is not approved, it doesn't matter. We will tell the developer why the application was rejected; Please modify the application according to the feedback and submit again. If you go to the media to attack us, it will certainly not help you.

This is a dynamic document. Newly submitted applications will lead to new problems, and new rules may be generated at any time. Maybe your application will touch this point. Therefore, the application review guide will be updated frequently. Please pay attention to the latest version of the document.

Finally, we cherish this platform and pay tribute to your works. We are really trying our best to create a perfect, sound and fair platform so that you can show your talents and get corresponding remuneration. Although this document is a "Don't Do" list, please keep that much shorter "Must Do" list in mind. According to our experience, no matter in terms of functions and user interfaces, users will indeed respond to perfect applications. If this makes you feel that our control is too strong, it is because we have promised users that we will use our products to give them a high-quality experience.

1、 Terms and Conditions

1.1 To develop applications for the microblog open platform, developers must abide by the microblog open platform developer agreement, microblog open platform design guidelines, and any agreements and contracts signed between developers and the microblog open platform. The following rules and examples are intended to help developers' applications gain recognition from the microblogging open platform, rather than modifying or deleting the terms of any other agreement.

2、 Function and performance

2.1 Collapsed applications will be rejected;

2.2 Applications with errors will be rejected;

2.3 Applications that do not conform to the developer's promotion will be rejected;

2.4 Applications without application documents or with hidden functions inconsistent with the description will be rejected;

2.5 Applications using non-public APIs will be rejected;

2.6 Applications that read or write data outside the specified container will be rejected;

2.7 Applications that download code in any way or form will be rejected;

2.8 Applications that install or release other executable codes will be rejected;

2.9 Demo, trial and beta applications will be rejected;

2.10 Applications that duplicate existing applications on the microblog open platform may be rejected, especially when there are many applications;

2.11 Applications that have no obvious purpose or provide no lasting entertainment value may be rejected;

2.12 Applications whose main content is marketing or advertising will be rejected;

2.13 Applications that cheat or have false functions and are not clearly marked will be rejected;

2.14 Applications browsing the network must use the web framework provided by the microblog open platform;

2.15 Applications that provide incorrect diagnosis or other inaccurate data will be rejected;

2.16 Developers who upload a large number of similar versions of applications to the microblog open platform will be removed from the developer project;

2.17 Applications using illegal file sharing will be rejected;

2.18 Applications designed as auxiliary tools for illegal gambling, including card counting, will be rejected;

2.19 Applications with the function of making anonymous or mischievous calls or sending similar SMS/MMS will be rejected;

2.20 Developers who develop applications that secretly collect user passwords or user private data will be removed from the microblog open platform;

2.21 Pop up windows are not allowed in the application;

2.22 If the access speed of application content is too slow, and the average response speed of content exceeds 6 seconds, it will be rejected.

3、 Metadata (name, description, rating, ranking, etc.)

3.1 Metadata applications with any platform name other than Weibo open platform will be rejected;

3.2 Applications with placeholder text will be rejected;

3.3 Applications with descriptions unrelated to application contents and functions will be rejected;

3.4 Applications whose directory and type are not suitable for application content will be rejected;

3.5 Developers who attempt to manipulate or cheat user comments or chart rankings by forging or other comments (or use other improper ways) will be removed from the microblog open platform.

4、 Account Login

4.1 It can support the login of microblog account and third-party account bound to microblog account. If there is a second login and registration with an account other than microblog account, the review will be rejected.

5、 Message notification

5.1 The application development message reminder push feature must use the standard API provided by the microblog open platform;

5.2 The user must be informed to subscribe or agree to accept when the application uses the message reminder push;

5.3 Applications that send false, deceptive or phishing information via message alerts will be rejected or removed from the shelves;

5.4 It is forbidden to push the promotion and advertising information below through message reminding;

5.5 Applications that abuse message reminder push and cause obvious harassment to users will be rejected or taken off the shelf;

5.6 It is forbidden to send virus, malware and program execution code via message reminder;

5.7 Applications that use message notification to send sensitive personal information or confidential information will be rejected;

5.8 The application cannot charge users who use the push notification service;

5.9 If an application can transmit viruses, files, computer codes or programs, and cause damage or interruption to the normal operation of APN services, the application will be rejected.

6、 Application content

6.1 Applications that are defamatory, personal offensive, narrow and despicable or against specific individuals or organizations will be rejected;

6.2 The real images of people or animals being killed, maimed, shot, stabbed, tortured and other injuries in the application will be rejected;

6.3 Applications depicting violence or child abuse will be rejected;

6.4 The role and words of "enemy" appearing in the application shall not point to a specific race, culture, a real government, enterprise or any other real entity;

6.5 Applications containing false, fraudulent or misleading statements will be rejected;

6.6 Applications that request, promote or encourage criminal or apparently reckless behavior will be rejected;

6.7 The application of true descriptions of weapons to encourage the illegal use or abuse of these weapons will be rejected;

6.8 Content that is too objectionable or vulgar in the application will be rejected, and the review of vulgar content shall comply with the Microblog User Convention;

6.9 Applications designed to irritate users or make people feel disgusted will be rejected;

6.10 Applications containing pornographic materials, which are defined in the Microblog Users Convention as "aimed at arousing sexual desire, explicit description or display of sexual organs or behaviors, but not aesthetic or emotional feelings", will be rejected;

6.11 Applications whose user generated content is mostly pornographic will be rejected;

6.12 References or comments involving religious, cultural or ethnic groups containing defamatory, offensive or selfish content, or applications that may cause harm or violence to specific groups will be rejected;

6.13 The application can contain or quote religious scriptures, and the quotation or translation provided by the application must be accurate and not misleading. Comments should have educational significance, can broaden the horizon, and should not be provocative; 



6.14 Gambling operations such as gambling and contests must be initiated by legally authorized application developers/companies;

6.15 Gambling operation rules such as gambling and competition must be noted in the application, and it must be clearly stated that Weibo is not the initiator, nor has it participated in activities in any way;

6.16 Lottery applications operated by developers must be within the legal scope, and lottery applications must have all the following characteristics: remuneration, probability and prizes;

6.17 Applications that allow users to directly purchase lottery tickets or raffle tickets will be rejected; 


6.18 Applications that contain content that can be donated to certified charities must be free of charge.

6.19 It is prohibited to develop marketing activity tools such as lottery forwarding or lottery.

7、 Trademarks and trade dress

7.1 The application must comply with all the terms and conditions of using the Sina trademark and copyright as well as the instruction manual of Sina trademark list;

7.2 For non official Weibo applications, 'Sina', 'Weibo'‘ Sina ',' weibo 'and other words;

7.3 Any application that misleads and implies that Sina is the source or provider of the application, or that Sina expresses approval of its quality or function in any form will be rejected;

7.4 Applications similar to or confused with existing Sina products or advertising themes will be rejected;

7.5 Any application that misspells the content of Sina trademark or copyright in the content authorized to use Sina trademark and copyright (for example, assistant for groom, SinA) will be rejected;

7.6 When using the protected third-party materials (trademarks, copyrights, trade secrets, other private content), a copy of copyright confirmation in the form of text is required.

8、 User interface 8.1 Applications must comply with all the terms and conditions explained in the Weibo User Interface Guidelines;

8.2 Applications that fail to correctly use the buttons, icons and other items provided by the system will be rejected as described in the Weibo User Interface Guidelines;

8.3 Applications with obvious experience defects will be rejected, including but not limited to: interface and page display errors, clutter, buttons, connections, navigation, etc. that cannot be used, obvious typos, picture errors, etc;

8.4 Applications that obviously plagiarize the interface, icons and other design elements of existing applications will be rejected.

9、 Advertising related

9.1 Applications that manually increase the number of application visits or Sina advertising clicks will be rejected;

9.2 Applications that are mainly designed to display advertisements will be rejected;

9.3 The application content and interface shall be free of advertisements irrelevant to the content of the application itself. The forms of advertisements include but are not limited to banners, text chains, etc.

10、 Payment

10.1 The application of microblog open platform must be free of charge, and paid services can be provided within the application;

10.2 Applications that use the payment capability provided by non Weibo platforms will be rejected;

10.3 Applications that purchase physical goods and services not used for the application will be rejected;

11、 Privacy protection

11.1 The application shall not transmit the data about the user without the user's permission or without providing the user with relevant information about how to use and where to use the data;

11.2 Applications that require users to share personal information such as e-mail address and birth date before using their functions will be rejected;

11.3 Applications that target minors for data collection will be rejected;

11.4 Applications that display user IDs to end users or any third party will be rejected;

11.5 Any application that uses the user ID for any purpose not approved by the terms of the microblog open platform will be rejected;

11.6 Developers who attempt to perform reflective search, tracking, association, mining, obtaining or using user ID, alias or other information obtained through the microblog open platform will be removed from the microblog open platform.

12、 Grab and aggregate

12.1 Applications that grab any information from Sina websites (such as sina.com.cn, weibo.com, etc.) or use the content and services of Sina websites for ranking will be rejected;

12.2 Applications can use approved Sina RSS feeds, such as Sina RSS feeds;

12.3 Applications that simply cut pages, aggregate content, or list links may be rejected.

13、 Legal constraints

13.1 Applications must comply with any legal requirements observed by users everywhere;

13.2 Developers are obliged to understand and comply with all local laws.

Review process

When your application is developed, it will enter the submission review stage. The following is a guide to the review process:

Under development

After creating an application, your application status is: Registered, Developing. When your application creation time, API calls, etc. meet certain conditions, you can click "Submit for Review" to apply for document review.

Copy to be reviewed

If the application wants to display the source address in the microblog information sent through the interface, it needs to apply for document review. "Failed to approve the application" is displayed by default.

Reviewed and approved

After the copy is approved, the source information of the microblog information sent through the application will be displayed on the microblog page, and the user will open the link address filled in the application background after clicking. At this time, the application background will display the "Submit for Review" button. Click it to apply for entering the application square.

Square to be reviewed

If the application wants to be displayed in the application square, it needs to apply for entering the square.

Square approved

After the square is approved, the application will be displayed in the corresponding category of the application square. At this time, the application background will display a prompt of "Online".

Square review rejected

After the square review is rejected, the application cannot be displayed on the application square page, but the source information will still be displayed in the microblog information sent through the application (provided that the copy passes the review).

AppKey Deactivation

After the Appkey is disabled, the application cannot call the interface for operation.

Audit time:

• 1. Review of copy source: the developer shall complete and give feedback within 30 working days after submitting the application copy for review (in case of special circumstances, the review cycle will be extended accordingly);
• 2. Application square review: The application square has been offline, and the application submitted by the application square is no longer accepted at present;
• 3. Secondary review of copy source: the review shall be completed within 30 working days after the developer submits the modified application (in case of special circumstances, the review cycle will be extended accordingly);

Developer Review Specification

1、 Individual Developer

premise

Fill in the developer information at open.weibo.com and verify through the email

Application materials

A. All information in the developer profile is complete and correct

B. Developer type is selected as Individual

C. Fill in the identity authentication information (including the real name, foreign nationality and ID number)

D. Submit ID photo (ID card/passport)

E. Fill in the mobile phone number and verify it by SMS

Review process

A. Developers submit online review applications and clear scanned copies of certificates

B. The reviewer verifies whether the developer's real name or ID number is consistent with the scanned ID card

C. The reviewer verifies whether the developer's identity information is true

D. Send audit result notification

2、 Enterprise Developer

premise

stay http://open.weibo.com/ Fill in developer information and verify it through email

Application materials

A. All information in the developer profile is complete and correct

B. Select "Company" as the developer type

C. Fill in identity authentication information (including company name and business license number)

D. Submit scanned copies of certificates (scanned copies of corporate ID card, business license and tax registration)

Review process

A. Developers submit online review applications and clear scanned copies of certificates

B. The reviewer verifies whether the developer's company name and business license number are consistent with the scanned certificate

C. The auditor verifies whether the legal person's identity information, business license information and tax registration information are true

D. Send audit result notification

3、 Plus V certification audit - cooperation website

Scope of certification

A. Comprehensive, industrial, e-commerce, life service, community, forum and other information type websites with independent domain names and legal qualifications.

B. Non website certification scope

• • a. Official websites and WAP sites of enterprises, software, products, service providers, institutions, activities, brands, online games, etc.
  • b. Websites involving pornographic, gambling, violence, and other inharmonious content.
  • c. Independent microblog website.

Certification requirements

A. Website Requirements

• a. Information websites

• • (1) The website must have the ICP filing number of the Ministry of Industry and Information Technology of the People's Republic of China.

• • (2) The website can be accessed normally, and the content of rich browsing is normal and complete.

• b. Community and forum type websites

• • (1) The website must have the ICP filing number of the Ministry of Industry and Information Technology of the People's Republic of China.

• • (2) The website can be accessed normally, and the content browsing display is normal and complete.

• • (3) The website users have a certain degree of activity, with more than 5000 registered users.

• c. Support Association Type Website

• • (1) The website must have the ICP filing number of the Ministry of Industry and Information Technology of the People's Republic of China.
  • (2) The website can be accessed normally, and the content browsing display is normal and complete.
  • (3) The website shall provide an official letter of authorization from the star, stating that this website is the official backup club/fan group website confirmed by the star, acknowledging the information published on the website, signing and affixing the official seal of the brokerage company.

B. Requirements for certification of microblog

• • a. Weibo nickname reflects the complete website name and highlights the identity of website account; Nicknames cannot contain well-known proper nouns and common phrases.

• • b. The Weibo avatar reflects the complete website logo.

• • c. Weibo content is mostly original and reflects website information.

• • d. Weibo content is guaranteed to be updated every day.

C. Certification description requirements

The website certification description includes: the industry or content location of the website, website name, website domain name+official microblog.

Certification process

A. Submit the certification application online and fill in the application information.

B. Download and upload test files to verify the authenticity of the website.

C. Waiting for staff review.

D. Audit completed.

• • a. After passing the review, the application microblog receives the "notice" and obtains the certification mark.

• • b. If the review is not passed, the application Weibo receives a "notice" to feedback the reason for the failure.

Certification penalty

A. Any website certified by the official Weibo will be cancelled after verification and confirmation for the first time with illegal content or behavior, and the punishment period is 30 days.

B. If the website is involved in illegal content or behavior for the second time, the official Weibo authentication will be permanently denied.

4、 V certification audit - microblog application

Scope of certification

Third party microblogging applications.

Certification requirements

A. Application requirements

The third-party microblog application passed the review of the application square.

B. Requirements for certification of microblog

• • a. The microblog nickname is consistent with the application name

• • b. The Weibo avatar is consistent with the application icon

• • c. Weibo content is closely related to application content

• • d. Weibo content is guaranteed to be updated every day

C. Certification description requirements

The content of the application microblog authentication description is the unified and standardized format of "microblog third-party application" application name "official microblog".

Certification process A. Submit the certification application online and fill in the application information.

B. Waiting for staff review.

C. Audit completed.

• • a. After passing the review, the application microblog receives the "notice" and obtains the certification mark.
  • b. If the review is not passed, the application Weibo receives a "notice" to feedback the reason for the failure.

5、 Secondary troubleshooting of developer identity

In order to better maintain the authenticity of the identity of the developers of the open platform, we will check the developers (including individuals and companies) that have passed the review at any time; The application developers with an average daily user number of more than or equal to 5000 will be checked at any time. If the application does not modify the developer information according to the above specifications, the open platform will take the following measures:

A、 Applications that have been published to the application channel will be offline from the application channel. At the same time, contact the developer to modify the offending content within 3 working days and resubmit for review;

B、 For applications that have not been published to the application channel, the source copy display will be canceled, and the developer will be contacted to modify the offending content within 3 working days and resubmit for review;

C、 Developers who violate the regulations can pass the corresponding review again after a week of observation and test after offline modification;

D、 For developers who fail to complete the modification within the required time, the corresponding interface permission will be stopped;

E、 For applications with serious violations, the corresponding interface usage rights will be immediately and directly stopped, and we reserve the right to appeal to relevant laws.

6、 Users' daily reports of wrongdoing Developer account handling

After investigation, evidence collection and verification, if it is determined that the developer's microblog account is involved in illegal behavior or the application developed is really a malicious application, the square and the file will be rejected immediately, and the developer will be notified to modify it within 48 hours; Applications that commit extremely serious crimes will immediately stop the authentication of the account.

Note: The above processing results will be publicized on the official account, forum and official WeChat group of the open platform.

7、 Audit time

A、 Developer identity review: the developer should complete the review and feedback within 30 working days after submitting the application;

B、 Weibo account verification: Currently, verification is no longer available.

Website Application Audit Specification

Application materials

The data shall be filled in completely, including the application icon corresponding to the website, correct application text description, developer contact information, etc.

Weibo connection

• 1. The cooperation website must add a connection/login portal, and use standard login buttons. The standard connection buttons of microblog include extra large, large, medium, small and icons: connection button logo
  • Accurate.
• 2. The cooperation website must provide easy access for users who log in from the website, which should be placed on the home page, login page, registration page, etc.
• 3. After clicking the Connect button, the user will be led to the authentication authorization page. The website must use OAuth for account login. The user clicks "direct login" or completes
  • After binding the account, jump to the home page or content page of the cooperation website. The welcome message must contain a microblog icon to indicate that the user logged in through the microblog account.
• 4. Users who connect for the first time must be guided to the connection settings page, and they need to be informed of which actions will send information to Weibo; Add on the user setting page of the cooperation website
  • Add "Weibo Settings", and the settings mainly include two parts:
  • A、 Bind/disconnect microblog: the process of exiting/disconnecting the cooperative website from microblog needs to be smooth and effective to ensure that users will not send any fresh messages to the home page after exiting or disconnecting
    • Things.
  • B、 Synchronization settings: tell the user which actions will send news.

Share button

The location and UI of the share button have an important impact on the sharing effect. The share button should be placed in an area that is convenient for users to see and where users are happy to interact, such as near the title of the article, near the comments at the end of the article, etc.

Enter Weibo Application Square

The website application is not displayed in the application square. Including account binding, sharing button and DZ plug-in.

Mobile Application Audit Specification

Application materials

The application materials are complete and correct, including standard and clear application icons, correct application descriptions, accurate developer information, etc. The application icon should be associated with the application, the application name should be consistent with the website name or the application content, and the application description should be consistent with the application function.

About Authorization

• 1. The authorization mechanism uses Oauth2.0 to automatically bounce the authorization page. The SDK download address of each version is: http://open.weibo.com/wiki/SDK ; Do not use solid color or default authorization background image on authorization page.

• 2. In some complex applications, users are not allowed to automatically share the use content to the user's microblog for each step of operation using the application, and users can choose to "share" or "cancel" by floating layer or other obvious prompt methods.

• 3. Do not use the user account to do any operation with his/her identity without his/her knowledge, including sending private messages, microblogs, @ messages, application notifications, application invitations, etc. to fans.

About concerns

When a user uses an application, the application itself shall not be set to automatically follow the official microblog page of the application or the developer's microblog page; Do not force users to pay attention.

Note: If the user is allowed to choose whether to follow the official microblog page or the developer microblog page by checking, the default selection is "followed" or the application with small prompt font will not be approved by the copywriting source

About Account Number

For applications that can bind multiple microblog accounts, developers need to monitor user behavior, and users cannot use multiple accounts to conduct malicious and illegal operations in the application.

Prohibited applications

• 1. Applications that disclose user privacy;

• 2. Application of aggressive words and behaviors;

• 3. Applications that threaten the microblog open platform;

• 4. Applications that maliciously create zombie fans, pay meaningless attention, buy and sell fans and other applications that are not conducive to the overall development of microblog;

• 5. Synchronous application of client, robot human and multi microblog platforms;

• 6. It involves feudal superstition applications;

• 7. Applications involving stock market orientation and payment transaction recharge;

• 8. Long term microblog tools, microblog data analysis, and timed functional applications;

• 9. Short term activity type application is not supported; If it is a long-term activity, please explain the activity rules in the application and confirm with Sina BD department.

Message sending

• 1. When a user logs in to the application page with a microblog account, the "User Authorization Application Confirmation Window" should pop up, with the content of "Grant the third party application the right to use the user account";

• 2. For Web applications, there should also be an Oauth authorization page;

• 3. After the user is authorized to log in, he/she shall not allow the user to log in or re register for a second time (for example, for some special reasons, he/she needs to keep the user's mailbox and other private information
• The user has the right to choose whether to provide more information);

• 4. The sharing function needs to set the default sharing content. Users can edit the sharing content, and the content shared to Weibo is consistent with the edited content. There is a success prompt after sharing.
• If the shared content contains pictures, the shared pictures shall not be irrelevant to the shared content or the application logo.
• Reference applications for sharing functions: Complete Video Tutorials of Winged Tiger CG, Online Car Market Bagua Test.

Application description

The application description shall be consistent with the application function.

Application materials

Application materials are complete, including standard application icons, correct application descriptions, accurate developer information, etc.

Application name protection

Developers are not allowed to register the domain names of well-known enterprises, websites, brands and other companies; In case of violation, the open platform has the right to withdraw the domain name.

• see Application review design specification

Enter Weibo Application Square

Premise: all application source document review conditions are met and document review has been passed

Application materials:

• 1. All information in the application data is complete and correct;

• 2. The application classification is correctly selected, and the label is consistent with the application function;

• 3. Submit comprehensive application screenshots, including screenshots of each step of operation, which should be clear, clear and in the right direction (for example, after the developer submits the application, it will enter the second review, and new screenshots can be used only after passing).

Application internal:

• 1. The application UI design is beautiful and meets the aesthetic standards of the public;

• 2. The application is easy to use: the main functions are obviously easy to choose, the steps are simple and do not repeat, and the threshold is low and easy to use;

• 3. The application home page has relevant application function introduction and description, informing the user of the functional characteristics of the application (the form can be customized according to the application itself, which can be specified);

• 4. The application function itself is closely related to Weibo (such as logging in with a Weibo account, sharing content to Weibo, and using Weibo user relationships);

• 5. In the process of using the application, there are clear prompts and user guidance for each step of operation;

• 6. It is not allowed to grab Weibo content and make local backup. It has the function of simultaneous deletion with Weibo.

Secondary troubleshooting

Routine inspection

In order to better maintain the application quality of the application channel, we will check the applications that have passed the review (including copy review and access to the application channel) at any time; The application with an average daily user number of more than or equal to 5000 will be checked at any time. If the application is not made according to the above specifications, the open platform will take the following measures:

• 1. Applications that have been published to the application channel will be offline from the application channel. At the same time, contact the developer to modify the offending content within 3 working days and resubmit for review;
• 2. For applications that have not been published to the application channel, the source copy display will be canceled, and the developer will be contacted to modify the offending content within 3 working days and resubmit for review;
• 3. Illegal applications can be reviewed again after a week of observation and test after offline modification;
• 4. For applications that fail to complete modification within the required time, the corresponding interface permission will be stopped;
• 5. For applications with serious violations, the corresponding interface access will be immediately and directly stopped, and we reserve the right to appeal to relevant laws;
• 6. For applications that can bind multiple user accounts, if a user is found in the application and uses his or her multiple accounts to do malicious and illegal operations, the application will be stopped immediately.
  • At the same time, contact the developer to modify the offending content within 3 working days, and resubmit for approval.

Note: In the process of secondary troubleshooting, the application functions and operations in each step should be consistent with the application screenshots submitted previously; In case of any modification @Weibo open platform , and resubmit for review.

User report

Third party application with ordinary authority: after investigation and evidence collection, it is confirmed that the application really belongs to evil application, and the square and the file will be rejected immediately; Notify the developer to warn, and publicize it on the official account of the microblog open platform, and the application will not pass the review within 90 working days; For applications that commit extremely serious crimes, the use of interfaces will be stopped immediately.

Partner permission application: after investigation, evidence collection and verification, it is determined that the application is really a malicious application, and the permission will be immediately reduced to ordinary, and the Plaza and the copywriter will reject it, and notify the developer to modify it within 48 hours; Applications that commit extremely serious crimes will immediately stop using the interface.

Note: The above processing results will be publicized on the official account of the open platform and the official WeChat group. Application case of doing evil

Special requirements for mobile applications

• 1. The promotional screenshots of mobile applications should reflect the functions associated with this client and Weibo, such as Weibo login, sharing to Weibo, etc;

• 2. The application link address needs to be filled in the client download page address: For iOS applications pending approval in the App Store, please fill in the URL address http://itunes.apple.com/cn/app/ ; Please fill in the URL address of the pending apps in the WindowsPhone App Store http://www.windowsphone.com/zh-CN/store 。

Professional Application Review Specification

About Authorization

• 1. The authorization mechanism uses the professional application format Oauth2.0 to automatically bounce the authorization page. The SDK download address of each version is: http://open.weibo.com/wiki/SDK Do not use solid color or default authorization background image on the authorization page;

• 2. In some complex applications, users are not allowed to automatically share the use content to the user's microblog in every step of operation using the application, and users can choose to "share" or "cancel" by floating layer or other obvious prompts;

• 3. Do not use the user account to do any operation with his/her identity without his/her knowledge, including sending private messages, microblogs, @ messages, application notifications, application invitations, etc. to fans;

• 4. The microblog professional application needs to operate the user account through "third-party authorization", and it is not allowed to store the user name and password in microblog.

About concerns

When a user uses an application, the application itself shall not be set to automatically follow the official microblog page of the application or the developer's microblog page; Do not force users to pay attention.

Note: If the user is allowed to choose whether to follow the official microblog page or the developer microblog page by checking, the default selection is "followed" or the application with small prompt font will not be approved by the copywriting source

About Account Number

For applications that can bind multiple microblog accounts, developers need to monitor user behavior, and users cannot use multiple accounts to conduct malicious and illegal operations in the application.

Professional application content regulations

• 1. Please do not use the words Sina and SINA in the application name and page;

• 2. Do not use standard microblog logo and variant versions in application icons and interfaces to avoid confusion for users;

• 3. The application home page defines the site attribution of the application and has relevant application function introductions and descriptions, informing users of the functional characteristics of the application (the form can be customized according to the application itself, and it can be specified);

• 4. The application page is embedded into the microblog page in the form of Iframe, which is 940px wide and 600-3000px high;; Please ensure that each page of the application can be displayed completely in the frame of the station;

• 5. The application page UI is required to be beautiful in design, reasonable in layout, clear in pictures, and easy to use. Do not add simple backgrounds to meet the size requirements of professional application pages, and there are no other third-party application functions logo， There is no link to content unrelated to the application, no large blank and other content that affects the user experience;

• 6. The application function itself is closely related to microblog (such as sharing content to microblog, following button, introducing microblog user relations, etc.);

• 7. In the process of using the application, there are clear prompts and user guidance for each step of operation (such as: share content to Weibo, follow button, introduce Weibo user relations, etc.);

• 8. It is not allowed to grab Weibo content and make local backup. It has the function of simultaneous deletion with Weibo;

• 9. In the application of Iframe, there is no scroll bar;

• 10. No content involving copyright issues;

• 11. The application details page shall specify the ownership of the application developer, and provide a real and available customer service phone number;

• 12. Macro social evaluation indicators such as "influence, social ROI, social rank" should not appear in the application;

• 13. The application should not have any indicators that conflict with the data in the "data center" of the professional microblog background;

• 14. There should be no comparison or deviation from other names, indicators and data in Weibo in the application;

• 15. For all foreground display applications, if there is an internal recommendation, the page clicked must be linked to the application details page, and it is not allowed to directly link to another application;

• 16. All background management applications shall not be directly linked to another application or have an external chain;

• 17. The same developer identity (including the same developer forging different identities) is not allowed to submit applications with the same function for launch repeatedly;

• 18. The application function is prohibited from plagiarism and malicious competition, and is completely consistent with the online application function in page design (layout, elements, etc.), and basically consistent with the main process;

• 19. The user interface of the application is not allowed to appear or link other third-party advertising information;

• 20. The application name, page, publicity and other relevant content are not allowed to appear official, exclusive, unique and other decorative words of microblog.

Prohibited applications

Applications with the following behaviors will not access professional applications:

• 1. Applications that disclose user privacy;

• 2. Application of aggressive words and behaviors;

• 3. Applications that threaten the microblog open platform;

• 4. Applications that maliciously create zombie fans and are not conducive to the overall development of microblog;

• 5. Synchronous application of client, robot human and multi microblog platforms;

• 6. It involves feudal superstition applications;

• 7. Applications involving stock market orientation;

• 8. Long Weibo tool.

Message sending

• 1. When a user logs in to the application page with a microblog account, the "User Authorization Application Confirmation Window" should pop up, with the content of "Grant a third party application permission to use the user account";

• 2. For Web applications, there should also be an Oauth authorization page;

• 3. After the user authorizes to log in, he/she shall not allow the user to log in for a second time or re register (if for some special reasons, he/she needs to keep other private information such as the user's mailbox, it shall be clearly indicated on the application page, and the user has the right to choose whether to provide more information);

• 4. The sharing function needs to set the default sharing content. Users can edit the sharing content, and the content shared to Weibo is consistent with the edited content. After sharing, there is a success prompt. If the sharing content contains pictures, the shared pictures must not be unrelated to the sharing content or be the application logo.

Application description

The application description shall be consistent with the application function.

Application materials

Application materials are complete, including standard application icons, correct application descriptions, accurate developer information, etc.

Toll application

The pricing strategy of the charging application does not cheat users, and must adopt the unified charging system of microblog. It is not allowed to lead to charging systems other than microblog.

Application name protection

Developers are not allowed to register the domain names of well-known enterprises, websites, brands and other companies; In case of violation, the open platform has the right to withdraw the domain name.

For professional version of application review design specification, please refer to Application Design Specification

Payment function audit specification

Note: At present, payment access is only open to "company developers", not "individual developers" for the time being.

Online "account authentication", filling specifications

• • • • • • • • • • • • • • • Picture 1

• • • • • • • • • • • • • • • Picture 2

• 1. Please fill in the real registration number of the legal person as follows
  • A、 The legal person registration number shall be consistent with the company's business license number;
  • B、 The name of the company shall be consistent with the name of the business license;
  • C、 The legal person's registered name shall be consistent with the tax registration name and the legal person's ID card name.

• 2. Uploading the scanned image shall be complete, clear and effective, and the following requirements shall be met:
  • A、 ID image size: only within 2M.
  • B、 ID image format: only PNG JPG。

• 3. Please be sure to fill in the true and effective bank account information. The bank account you fill in will be used as the future settlement account. The following requirements should be followed:
  • A、 Please ensure that the bank account is the company's corporate account;
  • B、 The company name and bank account should be consistent.

• • matters needing attention: Once the account authentication is approved, the company name and legal person registration number cannot be changed. Please fill in carefully!

Offline review of enterprise qualification

• You need to provide: a copy of the business license, a copy of the tax registration, and a copy of the corporate ID card, and ensure that the account authentication information filled in online is consistent with the paper qualifications provided offline.

• explain: Only if the account authentication information filled in online is consistent with the paper qualification provided offline, can it pass the audit! Please refer to Payment access process

Account Authentication audit time

• The review will be completed within 30 working days after Sina receives the paper qualification.

Apply online "payment application function" and fill in the specification

• • • • • • • • • • • • • • • • Picture 3

• 1. Security password: As the only voucher for your online use of payment function, please set and keep the security password carefully.
• 2. Callback address: When the user successfully pays, Weibo will call your callback address to inform you of the order status. (Note: If the non payment is successful, please refer to Payment interface Documentation).
• 3. Introduction to payment related functions: the functions that need to be paid in the application should be described in detail to facilitate the platform operation review.

• • matters needing attention: Once an application is approved, its name cannot be changed.

Application page specification

• • • • • • • • • • • • • • • • • Picture 4

• The application page must provide the customer service contact information of the application party (including online customer service - official Weibo account, telephone customer service, etc.), and must ensure that the customer service contact information is true and effective. If there is fraud and it has a great impact on users, the application payment function will be closed.

Contract signing specification

• At present, the payment function is only available to company developers, but not for individual developers.
• For company developers, after submitting the application for "application opening payment function" online, they need to sign the Sina Platform Application Cooperation Agreement offline. Only when the contract takes effect (that is, the contract has been stamped with the official seals of both parties) can the payment function be opened.

Approval time of application activation payment function

• The starting time of review is "the contract confirmed by both parties' business email". If the standard contract template is used and no changes are made, the payment review will be completed within 30 working days after both parties confirm the contract; If the standard contract template is not used and the contract terms need to be modified, both parties will complete the payment review within 90 working days after confirming the contract.

Common reasons for rejection

Icon screenshot class

1. The app (website) has no upload icon

Note: You must upload an 80 * 80 application (website) logo as an application (website) icon. Icons irrelevant to the application (website) or unclear will be rejected.

2. Please do not use official logos of Sina and Weibo

Note: You must upload your own logo for the application (website). If your product is not produced by Sina, please do not use any elements related to or similar to the official logo of Sina and Weibo to avoid misleading users.

3. The application icon is illegal, please replace it

Note: You must upload a regular icon as an application (website) icon. Any icon prohibited by laws and regulations or irrelevant to the application (website) function will be rejected.

4. The application screenshot is not clear and cannot be identified. Please upload again

Note: You must upload three (or more) different and clear screenshots of the application. The screenshots must cover the main functions of the application (website), and at least one screenshot must reflect the correlation between the application (website) and microblog.

5. Please show the app's functions related to Weibo in the app screenshot

Note: You must upload three (or more) clear application screenshots, and at least one screenshot should reflect that the application (website) has launched microblog cooperation components, such as microblog login, microblog sharing, etc.

Basic information

1. Please change the application name

Note: You must upload an application name with no more than 20 bytes. Any characters irrelevant to the application (website) or content that does not comply with laws and regulations will be rejected. The application name cannot use the website.

2. The app name is not related to the website name

Note: You must upload the characters you want to associate with the website name as the application name. Any characters unrelated to the application (website) function will be rejected.

3. Please improve the application (website) introduction

Note: You must upload an application (website) introduction with no less than 20 Chinese characters. The application introduction must briefly describe the application functions and usage methods. Any content irrelevant to the application (website) or content that does not comply with laws and regulations will be rejected.

4. The application introduction does not match the content of the application (website)

Note: You must upload the correct application introduction. The content of the application introduction must be consistent with the actual function of the application (website). Any text unrelated to the application (website) itself will be rejected.

5. Please fill in the URL with the client specific download page consistent with the application name or the address of the page in the software store, the online disk, and the forum page are invalid

Note: You must submit the official download channel, independent download page or app store download address of the app. Any app submitted in the form of online disk, forum page or hyperlink will be rejected, and the QR code alone as the download source cannot pass the review.

6. The URL address page content does not match the application name

Note: You must submit a URL address consistent with the application name. If the application name is A and the URL oriented application is B, then the application will be rejected.

7. Do not fill in the authorization page address directly at the URL, please fill in the page address with the authorization login button

Note: You must fill in the actual address of the application instead of the application authorization page at the application URL. When the user clicks the authorization button on the page, he or she will enter the application authorization page.

8. Please fill in the correct actual application (website) address

Note: You must upload the website address consistent with the description in the application description. Any microblog address or address unrelated to the application name and application description will be rejected.

9. Please fill in the correct website filing number in the website filing information item

Note: You must upload the correct website filing information. If the website filing number you submit is A, and the backup case number is B when you query the website of the Ministry of Industry and Information Technology, the website will be rejected.

10. No ICP filing on the website

Note: You must upload the correct website domain name. If the website domain name is not filed after being queried by the MIIT website, the website will be rejected. Overseas websites are required to upload legal qualification certificates issued by local website management agencies.

11. APP KEY type selection error

Note: You must select the correct application type to submit. If you do not know the application type, please read it carefully first http://open.weibo.com/ ; Once the application (website) type is confirmed, it cannot be modified. If your classification is wrong, please delete the wrong application and create a new one.

Platform policy

1. The built-in hardware client is not included in the application square

Note: If you are a hardware provider (including but not limited to personal communication equipment, various electronic terminals, TV, etc.), your application will not appear in the application square, please do not submit it to the square for review.

2. Cooperation websites/Xweibo applications are not displayed in the application square

Note: If you are a webmaster or network service provider, your website will not appear in the application square.

3. No interactive content with Weibo, such as sharing concerns, is not closely related to Weibo

Note: Your application (website) must have microblogging related operations. Please show the relevance of microblogging in the application screenshot and prominent position of the application (website). Any application (website) that has no or little relevance to microblogging will be rejected.

4. The application function does not comply with the open platform policy, please confirm the industry application qualification according to the platform policy

Note: In order to ensure that the services provided by your application meet the industry standards and the data is reliable, please confirm your qualification first. Please refer to http://t.cn/S6o1xM

5. The application involves content marketing. Please contact and communicate with Sina business colleagues for square review

Note: In order to ensure the authenticity of your marketing content and maintain a good microblog environment, please contact Sina Business before submitting for review

You can contact Weibo @Content Marketing Or contact email weineirong@sina.com

6. Does not meet the requirements of the developer agreement

Note: You must submit applications that comply with the developer agreement. Any applications that do not comply with the agreement will be rejected. If you do not understand the agreement, please read Application Developer Agreement 。

7. Application (website) content does not conform to relevant national regulations

Note: You must submit an application (website) that complies with national laws and regulations. Any application (website) that does not comply with relevant laws and regulations will be rejected.

8. Please complete the website content and submit again

Note: The website you submit must have more than 10 users. The forum requires that all sections have content displays, and the blog requires no less than 10 articles; Websites that do not meet the above criteria will be rejected.

9. The application page containing a large number of advertisements or promotional content will not be included in the application square

Note: If the application page contains other application friendship links, or other advertising promotion content, it will fail to pass the square review.

10. Short term activity applications cannot be approved as in station applications

Note: If your app is intended to serve an activity with a validity period of less than half a year, it will be rejected. You can try to add site components on the activity page and submit the web application approval.

Product function class

1. The application page cannot be opened. Please check the server status

Note: You must ensure that your app (website) page can be opened in a normal network environment. Apps (websites) that cannot be opened or take too long to load will be rejected.

2. No oauth authorization page

Note: You must ensure that your application (website) has authorized buttons and pages. Any application (website) without authorization or default authorization will be rejected.

3. Please use Oauth2.0 authorization for authorized login

Note: Your application (website) authorization must use the more secure Oauth2.0 authorization, and other authorization methods will be rejected.

4. Please use the Oauth2.0 authorization method and update the authorization page in the application screenshot

Note: Your application (website) authorization method must use a more secure Oauth2.0 authorization method. If you have used Oauth2.0 authorization method, please show your authorization method in the application screenshot.

5. Do not check by default or follow automatically

Note: You must ensure that your application does not have the behavior of checking or forcing users to automatically follow a microblog by default, and applications with the above functions will be rejected.

6. Do not check or automatically post microblog by default

Note: You must ensure that your application does not have the default behavior of checking microblogging or forcing users to automatically send microblogging content, and applications with the above functions will be rejected.

7. Other third-party functions included in ordinary web applications are not included in the application square

Note: You must ensure that your application only has its own functions or the function of jumping to Weibo, and any other additional functions or the function of jumping to a third-party website will be rejected.

8. For sharing function, please add a confirmation box for sharing content so that users can edit the shared content

Note: You must ensure that your app can provide a content publishing box when users use the app to publish Weibo content, and the content in the publishing box can be edited by users.

9. No cooperation component is seen online

Note: You must ensure that your website contains cooperation components related to microblogging such as authorized login or sharing. If you don't know what cooperation components are, please read here first: http://open.weibo.com/connect 。

10. The Weibo login button does not work properly. Please repair it before submitting it for review. The address of the cooperation component http://open.weibo.com/widgets?cat=wb

Note: Your Weibo login component does not respond or reports an error after clicking. If an error is reported, the site authentication fails, please check whether your callback address is configured incorrectly.

11. The sharing function in the application is not standardized

Note: You must ensure that the following behaviors do not exist in your application: the sharing content is irrelevant to the application, the sharing link does not point to the site application page, the sharing component does not use the application's own appkey, the user cannot know the sharing content before sharing, and the sharing content is automatically @ other users and cannot be changed.

12. Applications not open to all Weibo users will not be included in the square

Note: If your application is an internal enterprise application, an internal beta application or other applications not open to all Weibo users, such applications will not pass the square review.

Page design class

1. The application page is poorly designed and not included in the application square

Note: You must ensure that your page design is beautiful and generous. We hope you can bring users a good page experience. If you cannot provide a better page design for the time being, your application will not be displayed in the square. You can refer to Application review design specification 。

2. The site application page cannot be displayed in the site frame

Note: You must ensure that the application page can be completely and clearly displayed in the site application framework. If you don't know how to do it, please refer to: Application review design specification 。

3. Do not use solid color or default authorization background image on the website application authorization page

Note: You must ensure that the background image of the site application authorization page is beautiful, and the solid color or default authorization background image will be rejected. If you don't know what to do

Please refer to: Application Design Specification 。

4. Please use the in station application format Oauth2.0 to automatically jump the authorization page

Note: You must ensure that your application authorization page automatically pops up. If you don't know how to do it, please check: http://t.cn/aYzHgm 。

5. The size of the site application page does not meet the requirements of the site application review specification

Note: You must ensure that the width of your application in the station is 760px and the height is 600px-2000px. Applications that do not meet the above dimensions will be rejected.

Agreement copyright class

1. Do not use characters that may conflict with official microblog applications, such as "micro", "micro blog" and "V"

Note: You must ensure that your application name does not contain characters associated with the official microblog, such as "micro", "micro blog" and "V", to prevent misleading users.

2. In station applications include other third-party application functions or logos

Note: You must ensure that your site applications do not contain third-party application functions or logos other than the application's own functions and microblog functions. Applications that do not meet the above requirements will be rejected.

3. Please use microblog short link form to jump to external links

Note: When you need to jump links in your application, you must ensure that the links appearing in the application are presented in the form of microblog short chains.

4. Illegal application name

Note: You must ensure that your app name is legal and that you only have the certificate of property rights. Weibo has the right to take back any app name that preempts the trademark, brand and name.

5. The third-party microblog plug-in access is temporarily not supported

Note: You must ensure that your website access type is website, forum, blog, etc. The use of non microblogging plug-ins or separate microblogging station applications will be rejected.

6. For applications with brand exposure, you need to use the official account of the brand to create an application

Note: You must ensure that the application with brand exposure has relevant authorization qualification. If your application name is associated with brand A, the creator of this application must be an official microblog of brand A, and the authorization qualification of this brand (trademark ownership, business license, tax registration certificate and other relevant materials) is required to create an application using personal account or other unrelated accounts 。

7. Applications that obviously plagiarize the design of functions, interfaces or icons of existing applications will be rejected

Note: In order to protect the rights and interests of the online applications, applications that are seriously similar to the existing application page design, icons, and functions of the microblog open platform will be rejected.

Interface permission class

1. The number of application users does not meet the interface application conditions

Note: You must first ensure that your application has a certain number of users. No users or too few users can apply for an advanced interface.

2. The application function does not need to use this interface

Note: You must ensure that the application you develop really needs to apply for a high-level interface. If you are only a test interface, you cannot pass the application.

3. The application reason is inconsistent with the function realized by the interface

Note: You must ensure that the high-level interface you apply for matches the application function you expect to achieve. If the interface you apply for cannot achieve the application function you expect, you cannot apply.

4. The application reason is not sufficient, please specify the functions to be developed by the application

Note: To ensure the accuracy of the permissions you apply for, you need to provide detailed application function descriptions to apply for advanced interfaces. If your application reason for advanced interface is too general, you cannot apply.

5. If the number of application users is small, you cannot apply for advanced authorization level

Note: You must first ensure that your application really needs to apply for an authorization level. If there are no users or too few users of the application, it cannot pass the review. If you do not know the authorization level, please click here to learn: http://t.cn/zOjbn7e

see Other frequently asked questions