PLATFORM USAGE GUIDELINES
Have you taken care to review Twitter’s policies and set up your API access the right way? Does your service follow Twitter’s privacy and user control guidelines? If you can answer yes to these two questions, then you are ready to start using Twitter data and the Twitter API. Twitter’s Data Usage Guidelines provide the assistance needed to ensure that your use of Twitter data is compliant from Day 1 throughout the lifecycle of your service. We suggest reviewing these rules on a regular basis to make sure that your integration is operating in a way that is safe and beneficial to people on Twitter and the Twitter platform as a whole.
The use of the Twitter API and developer products to create spam, or engage in spammy behavior, is prohibited. You should review the Twitter Rules on spam, and ensure that your service does not, and does not enable users to violate our policies.
Services that perform write actions, including posting Tweets, following accounts, or sending Direct Messages, must follow the Automation Rules. In particular, you should:
Always get a user’s explicit consent before sending them automated replies or messages
Immediately respect user requests to opt-out of being contacted by you
Never perform bulk, aggressive, or spammy actions, including bulk following
Never post identical or substantially similar content across multiple accounts
If you’re operating an API-based bot account you must clearly indicate what the account is and who is responsible for it. You should never mislead or confuse people about whether your account is or is not a bot.
You may not use the Twitter API to measure the availability, performance, functionality, or usage of Twitter for benchmarking, competitive, or commercial purposes. For example, you should never use the Twitter API to:
Calculate aggregate Twitter user metrics, such as the total number of active users or accounts
Calculate aggregate Periscope metrics, such as total number of broadcast views
Calculate aggregate Twitter Tweet metrics, such as the total number of Tweets posted per day, or the number of user engagements or account engagements
Measure or analyze spam or security on Twitter, except as permitted in the Twitter Rules
Measure or analyze the responsiveness of Twitter
We support research that helps improve conversational health on Twitter. You may use the Twitter API and Twitter data to measure and analyze topics like spam, abuse, or other platform health-related topics for non-commercial research purposes. You may not develop, create, or offer commercial services using the Twitter API or Twitter data that measure, analyze, or attempt to identify behaviors or content which violate Twitter policies without express written permission from Twitter.
You must maintain the integrity of all Twitter content that you display publicly or to users of your service. If you don’t use Twitter for Websites to display content, then you must use the Twitter API to retrieve the most current version available for display. If displayed content ceases to be available through the Twitter API, then you must remove it from your service as soon as reasonably possible, or within 24 hours after the receipt of a removal request from Twitter, or the applicable Twitter user, or as otherwise required by applicable law.
There are specific rules you must follow if you display Twitter content offline. Follow the guidelines for using Tweets in broadcast if you display Tweets offline. Follow the guidelines for using Periscope Broadcasts if you display Periscope Broadcasts offline.
The best place to get Twitter data is directly from Twitter. Consequently, we restrict the redistribution of Twitter content to third parties. If you provide Twitter content to third parties, including downloadable datasets or via an API, you may only distribute Tweet IDs, Direct Message IDs, and/or User IDs (except as described below). We also grant special permissions to academic researchers sharing Tweet IDs and User IDs for non-commercial research purposes.
In total, you may not distribute more than 1,500,000 Tweet IDs to any entity (inclusive of multiple individuals associated with a single entity) within any 30 day period unless you have received written permission from Twitter. In addition, all developers may provide up to 50,000 public Tweets Objects and/or User Objects to each user of your service on a daily basis if this is done via non-automated means (e.g., download of spreadsheets or PDFs).
Academic researchers are permitted to distribute an unlimited number of Tweet IDs and/or User IDs if they are doing so on behalf of an academic institution and for the sole purpose of non-commercial research. For example, you are permitted to share an unlimited number of Tweet IDs for the purpose of enabling peer review or validation of your research. If you have questions about whether your use case qualifies under this category please submit a ticket via the API Policy Support form.
The best place to experience Twitter is on Twitter owned and operated (TOO) products. As such, we discourage developers from building services that replicate Twitter’s core user experience or features.
If you create a service that replicates Twitter’s core user experience or features you will be subject to additional rules beyond what is already included in the Developer Policy. In particular, you must:
Obtain our permission to have more than 100,000 user tokens. You may be subject to additional terms if this request is approved
Use the Twitter API for functionalities in your service that are substantially similar to Twitter features
Display a prominent link or button in your service that directs new users to Twitter’s account creation page
If you create a service that replicates Twitter’s core user experience or features you may not do any of the following:
Pay, or offer to pay, third parties for distribution. This includes offering compensation for downloads (other than transactional fees) or other mechanisms of traffic acquisition
Arrange for your service to be pre-installed on any other device, promoted as a "zero-rated" service, or marketed as part of a specialized data plan
Use Twitter content or other data collected from users to create or maintain a separate status update, social network, private messaging or live broadcasting database or service
Paying people to take actions on Twitter results in inauthentic conversations that degrade the health of the platform. As you use the Twitter API you may not sell or receive monetary or virtual compensation for any Twitter or Periscope actions. This includes, but is not limited to, Tweets, follows, unfollows, retweets, likes, comments, and replies.
You must clearly identify your service so that people can understand its source and purpose. Don’t use names, logos, or URLs that mask your service’s identity and features, or that falsely imply an affiliation with Twitter or third parties. Note that creating applications for the purpose of selling names, or to prevent others from using names, is prohibited.
You may not use any URL (including shortened URLs) for your service that directs people to:
You may only use and display the Twitter name and logo to identify Twitter as the source of Twitter content. You should never use the Twitter name and logo, the Twitter Official Partner Program badge, or any other similar marks or names in a manner that creates a false sense of endorsement, sponsorship, or association with Twitter. The Twitter Brand Resources contain detailed information to help you use the Twitter brand in the right way.
You may only use the Twitter Verified Account badge and any other enhanced user categorization as it is reported to you by Twitter through the API. This helps people know that the content your service displays is equivalent to that shown on Twitter.
You are allowed to advertise around Twitter content, although there are restrictions regarding how and where you are allowed to do so. To start, your advertisements can’t resemble or reasonably be confused by users as a Tweet or Periscope Broadcast. Other rules on advertising include:
You may advertise in close proximity to the Twitter timeline or a Periscope Broadcast (e.g., banner ads above or below timeline). But, there must be a clear separation between Twitter content and your advertisements.
You may advertise around and on sites that display Tweets and Periscope Broadcasts. But, you may not place any advertisements within the Twitter timeline or on or within Periscope Broadcasts on your service other than Twitter Ads or advertisements made available through the official Twitter Kit integration with MoPub.
Twitter reserves the right to serve advertising via the Twitter API. If you decide to serve Twitter Ads once we start delivering them via the API, we will share a portion of advertising revenue with you in accordance with the relevant terms and conditions.
You may not use Twitter content, or information obtained from the Twitter API, to target users with advertising outside of the Twitter platform. Anywhere. Ever.
You must contact us if you find that your service will require more than 1 million user tokens. Services that require more than 1 million user tokens may be subject to additional terms regarding Twitter API access.