CINXE.COM

<!DOCTYPE html><head><script type="text/javascript" src="/_static/js/bundle-playback.js?v=HxkREWBo" charset="utf-8"></script> <script type="text/javascript" src="/_static/js/wombat.js?v=txqj7nKC" charset="utf-8"></script> <script>window.RufflePlayer=window.RufflePlayer||{};window.RufflePlayer.config={"autoplay":"on","unmuteOverlay":"hidden"};</script> <script type="text/javascript" src="/_static/js/ruffle/ruffle.js"></script> <script type="text/javascript"> __wm.init("https://web.archive.org/web"); __wm.wombat("https://dev.twitter.com/terms/api-terms","20111109104511","https://web.archive.org/","web","/_static/", "1320835511"); </script> <link rel="stylesheet" type="text/css" href="/_static/css/banner-styles.css?v=S1zqJCYt" /> <link rel="stylesheet" type="text/css" href="/_static/css/iconochive.css?v=3PDvdIFv" />  <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <title>Developer Rules of the Road | Twitter Developers</title> <meta name="keywords" content="terms, tos"/> <meta name="description" content="Last Update - 1st of June 2011 Rules of the Road Twitter maintains an open platform that supports the millions of people around the world who are sharing and discovering what's happening now. We want to empower our ecosystem partners to build valuable businesses around the information flowing through Twitter."/> <script src="https://web.archive.org/web/20111109104511js_/https://platform.twitter.com/widgets.js" type="text/javascript"></script> <link rel="shortcut icon" href="/web/20111109104511im_/https://dev.twitter.com/sites/all/themes/twitter_commons/favicon.ico" type="image/x-icon"/> <link type="text/css" rel="stylesheet" media="all" href="/web/20111109104511cs_/https://dev.twitter.com/sites/default/files/css/css_258ec3672782fadbaf9030ffbcabd5e3.css"/> <script type="text/javascript" src="/web/20111109104511js_/https://dev.twitter.com/sites/default/files/js/js_6a0ca864189781d957cde9705a092b22.js"></script> <script type="text/javascript"> <![CDATA[//><!]]> </script> </head> <body id="page-node" class="not-front not-logged-in node-type-terms no-sidebars"> <div id="page"> <a href="#content-main" class="skip">Skip to Main Content Area</a> <div id="header-outer"> <div id="header"> <a href="/web/20111109104511/https://dev.twitter.com/" id="logo" title="Home"> Developers </a> <form action="/web/20111109104511/https://dev.twitter.com/terms/api-terms" accept-charset="UTF-8" method="post" id="search-theme-form"> <input id="search-q" name="search_theme_form" type="text" maxlength="128" size="15" value="Search" title="Enter search terms" placeholder="Search"/> <input id="search-submit" name="op" type="submit" value="Search"/> <input type="hidden" name="form_build_id" id="form-27c90c7ceeccaddf4b1f176f6bc70afb" value="form-27c90c7ceeccaddf4b1f176f6bc70afb"/> <input type="hidden" name="form_id" id="edit-search-theme-form" value="search_theme_form"/> </form> <ul id="title-nav"><li class="expanded first"><a href="/web/20111109104511/https://dev.twitter.com/status" title="">API Health</a><ul class="menu"><li class="leaf first"><a href="/web/20111109104511/https://dev.twitter.com/status" title="">API Status</a></li> <li class="leaf last"><a href="/web/20111109104511/https://dev.twitter.com/issues" title="">API Issues</a></li> </ul></li> <li class="leaf"><a href="/web/20111109104511/https://dev.twitter.com/blog" title="">Blog</a></li> <li class="leaf"><a href="/web/20111109104511/https://dev.twitter.com/discussions" title="">Discussions</a></li> <li class="expanded"><a href="/web/20111109104511/https://dev.twitter.com/docs" title="">Documentation</a><ul class="menu"><li class="leaf first"><a href="/web/20111109104511/https://dev.twitter.com/docs" title="">Overview</a></li> <li class="leaf"><a href="/web/20111109104511/https://dev.twitter.com/docs/api" title="">REST API</a></li> <li class="leaf"><a href="/web/20111109104511/https://dev.twitter.com/docs/streaming-api" title="Streaming API">Streaming API</a></li> <li class="leaf"><a href="/web/20111109104511/https://dev.twitter.com/docs/twitter-for-websites" title="">Twitter for Websites</a></li> <li class="leaf last"><a href="/web/20111109104511/https://dev.twitter.com/docs/recent" title="">Recently updated</a></li> </ul></li> <li class="leaf last"><a href="/web/20111109104511/https://dev.twitter.com/user/login?destination=node%2F110" title="">Sign in</a></li> </ul> </div> </div> <div id="content-outer"> <div id="breadcrumbs"> <div class="breadcrumb"><a href="/web/20111109104511/https://dev.twitter.com/">Home</a> → <a href="/web/20111109104511/https://dev.twitter.com/docs">Documentation</a><div><a href="https://web.archive.org/web/20111109104511/http://twitter.com/share" data-count="none" data-related="twitterapi" class="twitter-share-button">Tweet</a></div></div> </div> <h1 id="title">Developer Rules of the Road</h1> <div id="content-inner"> <div id="content-main"> <div> <p><em>Last Update - 1st of June 2011</em></p> <h2>Rules of the Road</h2> <div class="section"> <p>Twitter maintains an open platform that supports the millions of people around the world who are sharing and discovering what's happening now. We want to empower our ecosystem partners to build valuable businesses around the information flowing through Twitter. At the same time, we aim to strike a balance between encouraging interesting development and protecting both Twitter's and users' rights.</p> <p>So, we've come up with a set of Developer Rules of the Road ("<strong>Rules</strong>") that describe the policies and philosophy around what type of innovation is permitted with the content and information shared on Twitter.</p> <p>The Rules will evolve along with our ecosystem as developers continue to innovate and find new, creative ways to use the Twitter API, so please check back periodically to see the most current version. Don't do anything prohibited by the Rules, but talk to us if you think we should make a change or give you an exception.</p> <p>If you will eventually need more than 5 million user tokens for your projects, you will need to talk to us directly about access to the Twitter API.</p> </div> <h2>I. Twitter Content</h2> <div class="section"> <p>1. All use of the Twitter API and content, documentation, code, and related materials made available to you on or through Twitter ("<strong>Twitter Content</strong>") is subject to and must comply with these Rules. As a reminder, you and your Service are subject to the <a href="https://web.archive.org/web/20111109104511/http://twitter.com/tos">Twitter Terms of Service</a>.</p> <p>2. You may use the Twitter API and Twitter Content in connection with the products or services you provide (your "<strong>Service</strong>") to search, display, analyze, retrieve, view, and submit information to or on Twitter. You may use the Twitter name or logos and other brand elements that Twitter makes available in order to identify the source of Twitter Content ("<strong>Twitter Marks</strong>") subject to these Rules.</p> <p>3. Your use of the Twitter API and Twitter Content are subject to certain limitations on access, calls, and use as set forth in the Rules, on dev.twitter.com, or as otherwise provided to you by Twitter. If Twitter believes that you have attempted to exceed or circumvent these limitations, your ability to use the Twitter API and Twitter Content may be temporarily or permanently blocked. Twitter may monitor your use of the Twitter API to improve the Twitter service and to ensure your compliance with these Rules.</p> <p>4. You will not attempt or encourage others to:</p> <ol style="list-style-type: upper-alpha"> <li>sell, rent, lease, sublicense, redistribute, or syndicate access to the Twitter API or Twitter Content to any third party without prior written approval from Twitter. <ul> <li>If you provide an API that returns Twitter data, you may only return IDs (including tweet IDs and user IDs).</li> <li>You may export or extract non-programmatic, GUI-driven Twitter Content as a PDF or spreadsheet by using "save as" or similar functionality. Exporting Twitter Content to a datastore as a service or other cloud based service, however, is not permitted.</li> </ul> </li> <li>remove or alter any proprietary notices or marks on the Twitter API or Twitter Content; </li> <li>use or access the Twitter API for purposes of monitoring the availability, performance, or functionality of any of Twitter's products and services or for any other benchmarking or competitive purposes; or</li> <li>use Twitter Marks in a manner that creates a sense of endorsement, sponsorship, or false association with Twitter. You may not use Twitter Marks as part of the name of your company or Service, or in any product, service, name field or logos created by you. All use of Twitter Marks, and all goodwill arising out of such use, will inure to Twitter's benefit.</li> <li>use or access the Twitter API to aggregate, cache (except as part of a Tweet), or store place and other geographic location information contained in Twitter Content.</li> <li>charge a premium for access to tweets via SMS other than your Service's standard data and usage rates.</li> </ol> <p>5. Your Service may be an application or client that provides major components of a Twitter-like end user experience (a "<strong>Client</strong>"). An example of a Client is a downloadable application that displays user timelines and allows users to create and search for tweets. If so, certain additional terms apply, including:</p> <ol style="list-style-type: upper-alpha"> <li>Your Client must use the Twitter API as the sole source for features that are substantially similar to functionality offered by Twitter. Some examples include trending topics, who to follow, and suggested user lists.</li> <li>You may not pay, or offer to pay, third parties for distribution of your Client. This includes offering compensation for downloads (other than transactional fees), pre-installations, or other mechanisms of traffic acquisition. </li> <li>Your Client cannot frame or otherwise reproduce significant portions of the Twitter service. You should display Twitter Content from the Twitter API.</li> <li>Do not store non-public user profile data or content.</li> <li>You may not use Twitter Content or other data collected from end users of your Client to create or maintain a separate status update or social network database or service.</li> </ol> <p>6. You do not have a license to Twitter Content submitted through your Service other than the rights granted in the Rules.</p> </div> <h2>II. Principles</h2> <div class="section"> <p>We ask that you and your Service follow four principles:</p> <ul> <li>Don't surprise users</li> <li>Don't create or distribute spam</li> <li>Respect user privacy</li> <li>Be a good partner to Twitter</li> </ul> <h3>1. Don't surprise users</h3> <ol style="list-style-type: upper-alpha"> <li>Maintain the integrity of Tweets. There is a lot of information packed into Tweets even though they are just 140 characters long (e.g., links to usernames). The <a href="/web/20111109104511/https://dev.twitter.com/pages/display_guidelines">Display Guidelines</a> are a part of the Rules and provide guidance on how to best convey all the intended information in a Tweet.</p> <p>A few highlights:</p> <ul> <li>Don't edit or revise user-generated content delivered through the API except as necessary due to technical limitations or requirements of any networks, devices, services, or media.</li> <li>Identify the user that authored or provided a Tweet unless you are either providing Tweets in an aggregate form, or need to make Tweets anonymous due to user privacy or security concerns.</li> </ul> </li> <li>Get users' permission before: <ul> <li>sending Tweets or other messages on their behalf. A user authenticating through your application does not constitute consent to send a message.</li> <li>modifying their profile information or taking account actions (including following, unfollowing, and blocking) on their behalf.</li> <li>adding hashtags, annotations data, or other content to a user's Tweet. If your application allows users to send Tweets or other content to Twitter, show the user exactly what will be published.</li> <li>republishing Twitter Content accessed through means other than via the Twitter API or other tools that may be provided to you by Twitter, or in a manner inconsistent with the Display Guidelines.</li> </ul> </li> <li>Your Service should not: <ul> <li>use business names and/or logos in a manner that can mislead, confuse, or deceive users. For more information on use of Twitter Marks, see our trademark rules <a href="https://web.archive.org/web/20111109104511/http://support.twitter.com/articles/77641">here</a></li> <li>confuse or mislead users about the source or purpose of your application.</li> <li>use as its Application Website URL an unrelated URL, a site intended to entice or encourage users to violate our rules, a spam or malware site, or a shortened URL to mask the true destination.</li> <li>replicate, frame, or mirror the Twitter website or its design.</li> <li>impersonate or facilitate impersonation of others in a manner that can mislead, confuse, or deceive users.</li> </ul> </li> <li>Respect the privacy and sharing settings of Twitter Content. Do not share, or encourage or facilitate the sharing of protected Twitter Content. Promptly change your treatment of Twitter Content (for example, deletions, modifications, and sharing options) as changes are reported through the Twitter API.</li> </ol> <h3>2. Don't create or distribute spam</h3> <ol style="list-style-type: upper-alpha"> <li>Spam can take many forms. Please abide by the spam rules <a href="https://web.archive.org/web/20111109104511/http://support.twitter.com/articles/18311#spam">here</a>.</li> <li>If your application performs automatic actions (including Tweeting or other content updates), make sure you comply with the Automation Rules found <a href="https://web.archive.org/web/20111109104511/http://support.twitter.com/articles/76915">here</a>.</li> <li>Do not mass-register applications. This includes: <ul> <li>creating tokens/applications for the purpose of preventing others from using or selling those names, or other commercial use.</li> <li>using feeds of third-party content to update and maintain accounts under the names of those third parties.</li> <li>submitting multiple applications with the same function under different names for the purpose of name squatting.</li> </ul> </li> <li>Do not facilitate or encourage the publishing of: <ul> <li>links to malicious content</li> <li>pornographic or obscene images to user profile images and background images</li> </ul> </li> </ol> <h3>3. Respect user privacy</h3> <ol style="list-style-type: upper-alpha"> <li>Your Service must display a privacy policy. Clearly disclose what you are doing with information you collect from users.</li> <li>Clearly disclose when you are adding location information to a user's Tweets, whether as a geotag or annotations data. Be clear about whether you are adding a place or specific coordinates. If your application allows users to Tweet with their location be sure that it complies with the best practices found <a href="/web/20111109104511/https://dev.twitter.com/pages/geo_dev_guidelines">here</a>.</li> <li>You should not solicit another developer's consumer keys or consumer secrets especially if they will be stored or used for actions outside of that developer's control. Keys and secrets that are compromised will be reset by Twitter. For example, online services that ask for these values in order to provide a "tweet-branding" service are not allowed.</li> <li>Do not facilitate or encourage the publishing of private or confidential information.</li> </ol> <h3>4. Be a good partner to Twitter</h3> <ol style="list-style-type: upper-alpha"> <li>If you display Tweets in an offline context, do so according to the guidelines found <a href="https://web.archive.org/web/20111109104511/http://support.twitter.com/articles/114233">here</a>.</li> <li>Respect the features and functionality embedded with or included in Twitter Content or the Twitter API. Do not attempt to interfere with, intercept, disrupt, filter, or disable any features of the Twitter API or Twitter service, and you should only surface actions that are organically displayed on Twitter. <ul> <li>For example, your Service should execute the unfavorite and delete actions by removing all relevant messaging and Twitter Content, not by publicly displaying to other end users that the Tweet was unfavorited or deleted.</li> </ul> </li> <li>If your application causes or induces user accounts to violate the <a href="https://web.archive.org/web/20111109104511/http://support.twitter.com/articles/18311">Twitter Rules</a> (for example, by retweeting spam updates, repeatedly posting duplicate links, etc.), it may be suspended or terminated. We've provided some guidance in our <a href="https://web.archive.org/web/20111109104511/http://support.twitter.com/articles/79901">Abuse Prevention and Security help page</a>.</li> <li>Respect the intellectual property rights of others.</li> <li>Do not use the Twitter Verified Account badge, Verified Account status, or any other enhanced user categorization on Twitter Content other than that reported to you by Twitter through the API.</li> <li>Twitter may suspend or revoke access if we believe you are in violation of the Rules or the spirit of these principles. If you are suspended, do not apply for or register additional API tokens.</li> </ol> </div> <h2>III. Twitter Functionality in your Service</h2> <div class="section"> <h3>1. Twitter Login</h3> <p>End users must be presented with the option to log into Twitter via the OAuth protocol. End users without a Twitter account should be given the opportunity to create a new Twitter account as provided by Twitter. You must display the Connect with Twitter option at least as prominently as the most prominent of any other third party social networking sign-up or sign-in marks and branding appearing on you Service.</p> <h3>2. General</h3> <ol style="list-style-type: upper-alpha"> <li>If you allow end users to create social updates from your own social service or a third party social networking, micro-blogging, or status update provider integrated into the your Service ("<strong>Update</strong>"), you must also display a prominent option to publish that content (or a link if the Update is not text or longer than 140 characters) to Twitter. Only link back to the same Update or content on the other service if the Update is longer than 140 characters.</li> <li>All URLs referencing content in the Update (for example, a web page, photo, video, or text longer than 140 characters) should direct users back to the page where that content is displayed, rather than any interstitial or intermediate page. You can require users to sign-in to access that page, but the content cannot otherwise be restricted from being viewed.</li> <li>If your service displays Updates commingled with Tweets, you must ensure that Tweets reference Twitter as the source.</li> </ol> <h3>3. Twitter Identity</h3> <p>Once an end user has authenticated via Connect with Twitter, you must clearly display the end user's Twitter identity. Twitter identity includes visible display of the end user's avatar, Twitter user name, and the Twitter "bird" mark. Displays of the end user's followers on your Service must clearly show that the relationship is associated with the Twitter service.</p> </div> <h2>IV. Commercial Use</h2> <div class="section"> <p>It is our goal to provide you, our ecosystem partner, with a policy that is clear and transparent about what you can do to monetize your Service. This is best summed up in two principles:</p> <ul> <li>respect user content -- Tweets may be used in advertisements, not as advertisements.</li> <li>respect user experience -- build your service around the timeline, not in the timeline.</li> </ul> <ol> <li><strong>Twitter Ads</strong>. Twitter reserves the right to serve advertising via its APIs ("<strong>Twitter Ads</strong>"). If you decide to serve Twitter Ads once we start delivering them, we will share a portion of advertising revenue with you per our then-current terms and conditions.</li> <li><strong>Advertising Around Twitter Content</strong> <ol style="list-style-type: upper-alpha"> <li>We encourage you to create advertising opportunities around Twitter content that are compliant with these Rules. In cases where Twitter Content is the primary basis of the advertising sale, we require you to compensate us (recoupable against any fees payable to Twitter for data licensing). For example, you may sell sponsorships or branding around gadgets or iframes that include Tweets and other customized visualizations of Twitter with prior permission.</li> <li>You may generally advertise around and on sites that display Tweets, but you may not place any advertisements within the Twitter timeline on your Service other than Twitter Ads.</li> <li>Your advertisements cannot resemble or reasonably be confused by users as a Tweet. For example, ads cannot have tweet actions like ReTweet, Favorite, and Reply. And you cannot sell tweet actions or the placement of tweet actions on your Service.</li> <li>You may advertise in close proximity to the Twitter timeline (e.g., banner ads above or below timeline), but there must be a clear separation between Twitter content and your advertisements.</li> </ol> </li> <li><strong>Using Twitter Content</strong>. Get the users' permission before: <ul> <li>using their content on a commercial durable good or product (for example, using a Tweet on a t-shirt or a poster or making a book based on someone's Tweets);</li> <li>creating an advertisement that implies the sponsorship or endorsement on behalf of the user; or</li> <li>using content in a manner that is inconsistent with the Display Guidelines and would require the user鈥檚 permission under applicable law.</li> </ul> </li> </ol> </div> <h2>V. Other Legal Terms</h2> <div class="section"> <h3>1. Termination.</h3> <p>You may terminate any license in these Rules at any time by ceasing your access to the Twitter API and use of any Twitter Content, and deleting all copies of the Twitter API and Twitter Content as described below. Twitter may immediately suspend your access to the Twitter API or any Twitter Content (or if necessary, terminate this agreement with you) at any time, and without notice to you if you breach any term or condition in the Rules or otherwise engage in activities that Twitter reasonably determines are likely to cause liability to Twitter. Twitter may also terminate any licenses hereunder for any reason (including by email to the address associated with your account). Twitter will not be liable for any costs, expenses, or damages as a result of its termination of this agreement. Upon termination of this agreement, you will promptly cease accessing and using the Twitter API and Twitter Content and will delete all Twitter Content and any information derived therefrom and all copies and portions thereof, in all forms and types of media from your Service. Sections 1(4) and V of these Rules will survive the termination of this agreement.</p> <h3>2. Confidentiality.</h3> <p>You may be given access to certain non-public information, software, and specifications relating to the Twitter API ("Confidential Information"), which is confidential and proprietary to Twitter. You may use this Confidential Information only as necessary in exercising your rights granted in these Rules. You may not disclose any of this Confidential Information to any third party without Twitter's prior written consent. You agree that you will protect this Confidential Information from unauthorized use, access, or disclosure in the same manner that you would use to protect your own confidential and proprietary information of a similar nature and in any event with no less than a reasonable degree of care.</p> <h3>3. Ownership; Feedback.</h3> <p>3.1 <em>Twitter</em>. You expressly acknowledge that Twitter and its end users retain all worldwide right, title and interest in and to the Twitter Content, including all intellectual property rights therein. You also acknowledge that as between you and Twitter, Twitter owns all right, title and interest in and to the Twitter API, Twitter Marks, and the Twitter service (and any derivative works or enhancements thereof), including but not limited to all intellectual property rights therein. You agree not to do anything inconsistent with such ownership. Any rights not expressly granted herein are withheld. You agree that you will not challenge Twitter's ownership of, the validity of any license to use, or otherwise copy or exploit the Twitter Marks during or after the termination of this agreement except as specifically authorized herein. If you acquire any rights in the Twitter Marks or any confusingly similar marks, by operation of law or otherwise, you will, at no expense to Twitter, immediately assign such rights to Twitter.</p> <p>3.2 <em>You</em>. As between you and Twitter, you retain all worldwide right, title and interest in and to your Service, excluding the Twitter API, Twitter Marks, and the Twitter Service (and any derivative works or enhancements thereof), including but not limited to all intellectual property rights therein. You may provide Twitter with comments concerning the Twitter Content or Twitter API or your evaluation and use thereof. You agree that Twitter and its designees will be free to copy, modify, create derivative works, publicly display, disclose, distribute, license and sublicense, incorporate, and otherwise use the feedback, including derivative works thereto, for any and all commercial and non-commercial purposes with no obligation of any kind to you.</p> <h3>4. Updates.</h3> <p>Twitter may update or modify the Twitter API, Rules, and other terms and conditions, including the Display Guidelines, from time to time its sole discretion by posting the changes on this site or by otherwise notifying you (such notice may be via email). You acknowledge that these updates and modifications may adversely affect how your Service accesses or communicates with the Twitter API. If any change is unacceptable to you, your only recourse is to terminate this agreement by ceasing all use of the Twitter API and Twitter Content. Your continued access or use of the Twitter API or any Twitter Content will constitute binding acceptance of the change.</p> <h3>5. Representations and Warranties; Disclaimer.</h3> <p>5.1 <em>Representations and Warranties</em>. You represent and warrant that: </p> <ol style="list-style-type: upper-alpha"> <li>you have the necessary power and authority to enter into this agreement, and that the performance of your obligations will not constitute a breach or otherwise violate any other agreement or the rights of any third party arising therefrom;</li> <li>you will maintain throughout the term of this agreement all rights and licenses that are required with respect to your Service; and </li> <li>your Service and its use, distribution, sale and license, including the use of any license hereunder, does and will continue to comply with all applicable foreign, federal, state, and local laws, rules, and regulations.</li> </ol> <p>5.2 <em>Disclaimer</em>. THE TWITTER CONTENT, TWITTER API, AND ANY OTHER TWITTER PRODUCTS AND SERVICES PROVIDED HEREUNDER ARE PROVIDED "AS IS" AND ON AN "AS-AVAILABLE" BASIS, WITHOUT WARRANTY OF ANY KIND. TWITTER DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENT, FITNESS FOR A PARTICULAR PURPOSE, AND ANY WARRANTIES OR CONDITIONS ARISING OUT OF COURSE OF DEALING OR USAGE OF TRADE. TWITTER DOES NOT WARRANT THAT THE TWITTER CONTENT AND TWITTER API AND ANY OTHER TWITTER PRODUCTS AND SERVICES PROVIDED HEREUNDER WILL MEET ALL OF YOUR REQUIREMENTS OR THAT USE OF SUCH TWITTER CONTENT AND TWITTER API BE ERROR-FREE UNINTERRUPTED, VIRUS-FREE, OR SECURE.</p> <h3>6. Limitation of Liability.</h3> <p>IN NO EVENT WILL TWITTER BE LIABLE TO YOU FOR ANY SPECIAL, INCIDENTAL, EXEMPLARY, PUNITIVE OR CONSEQUENTIAL DAMAGES (INCLUDING LOSS OF USE, DATA, BUSINESS OR PROFITS) ARISING OUT OF OR IN CONNECTION WITH THIS AGREEMENT OR YOUR USE OF THE TWITTER API, TWITTER CONTENT, OR OTHER TWITTER PRODUCTS AND SERVICES WHETHER SUCH LIABILITY ARISES FROM ANY CLAIM BASED UPON CONTRACT, WARRANTY, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY OR OTHERWISE, AND WHETHER OR NOT YOU HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. THE FOREGOING LIMITATIONS WILL SURVIVE AND APPLY EVEN IF ANY LIMITED REMEDY SPECIFIED IN THIS AGREEMENT IS FOUND TO HAVE FAILED ITS ESSENTIAL PURPOSE. IN ANY CASE, TWITTER'S AGGREGATE LIABILITY UNDER THIS AGREEMENT WILL NOT EXCEED THE GREATER OF ONE HUNDRED DOLLARS ($100) OR THE AGGREGATE FEES YOU PAID FOR ACCESS TO THE TWITTER API IN THE LAST YEAR.</p> <h3>7. Indemnification. </h3> <p>You will indemnify, defend, and hold Twitter, its subsidiaries, affiliates, officers, and employees, harmless from any and all claims, damages, losses, liabilities, actions, judgments, costs, and expenses (including reasonable attorneys' fees) brought by a third party arising out of or in connection with: (a) any act or omission by you, in connection with your use of the Twitter Content, the Twitter API, or the Twitter Marks; (b) your use of the Twitter Content, the Twitter API, or the Twitter Marks other than as expressly allowed by this agreement; (c) your breach or alleged breach of any of the terms, restrictions, obligations or representations under this agreement; or (d) your Service. You will assume control of the defense and settlement of any claim subject to indemnification by you. Twitter may, however, at any time elect to take over control of the defense and settlement of any such claim. In any event, you will not settle any such claim without Twitter's prior written consent.</p> <h3>8. Miscellaneous.</h3> <p>These Rules constitute the entire agreement among the parties with respect to the subject matter and supersedes and merges all prior proposals, understandings and contemporaneous communications. Any modification to the Rules by you must be in a writing signed by both you and Twitter. You may not assign any of the rights or obligations granted hereunder, voluntarily or by operation of law (including without limitation in connection with a merger, acquisition, or sale of assets) except with the express written consent of Twitter, and any attempted assignment in violation of this paragraph is void. This agreement does not create or imply any partnership, agency or joint venture. This agreement will be governed by and construed in accordance with the laws of the State of California, without regard to or application of conflicts of law rules or principles. All claims arising out of or relating to this agreement will be brought exclusively in the federal or state courts of San Francisco County, California, USA, and you consent to personal jurisdiction in those courts. No waiver by Twitter of any covenant or right under this agreement will be effective unless memorialized in a writing duly authorized by Twitter. If any part of this agreement is determined to be invalid or unenforceable by a court of competent jurisdiction, that provision will be enforced to the maximum extent permissible and the remaining provisions of this agreement will remain in full force and effect.</p> </div> <div class="section"> <p>View the <a href="/web/20111109104511/https://dev.twitter.com/terms/api-terms/archive">API Terms of Service: Archive</a> or <a href="/web/20111109104511/https://dev.twitter.com/terms/api-terms/diff">the most recent changes</a>.</p> </div></div> </div> </div> </div> <div id="footer-outer"> <div id="footer"> <a href="https://web.archive.org/web/20111109104511/http://twitter.com/twitterapi" data-show-count="false" class="twitter-follow-button" data-text-color="999999" data-link-color="0080A6">Follow @twitterapi</a><ul class="menu"><li class="leaf first active-trail"><a href="/web/20111109104511/https://dev.twitter.com/terms/api-terms" title="Developer Rules of the Road" class="active">API Terms</a></li> <li class="leaf"><a href="/web/20111109104511/https://dev.twitter.com/status" title="Twitter API Status">API Status</a></li> <li class="leaf"><a href="/web/20111109104511/https://dev.twitter.com/blog" title="Twitter Developer blog">Blog</a></li> <li class="leaf"><a href="/web/20111109104511/https://dev.twitter.com/discussions" title="Twitter Development discussions">Discussions</a></li> <li class="leaf"><a href="/web/20111109104511/https://dev.twitter.com/docs" title="Twitter development documentation">Documentation</a></li> <li class="leaf last"><a href="https://web.archive.org/web/20111109104511/http://www.acquia.com/" title="Acquia">A Drupal community site supported by Acquia</a></li> </ul> </div> </div> </div><script type="text/javascript"> <![CDATA[//><!]]> </script> </body> </html>