LAST UPDATED: MARCH 9, 2020

Overview

Our goal is to provide developers with a set of tools to create products that will enrich the Riot Games community and provide better player experiences. When working with the Riot Games API and other Developer Tools, we have several conditions set forth in our Terms of Use and Legal Jibber Jabber. Please be sure that you are familiar with those documents prior to developing your product. In addition to those documents, we also provide the following General Policies that all products in the Riot Games third-party ecosystem must adhere to. Failure to meet these policies may result in either suspension or cancellation of your API access or legal recourse.

In order for these policies to best serve the Riot Games ecosystem, they will inevitably change over time. As a result, developers must remain up to date with these policies. Developers are expected to adhere to these policy changes as they arise.

Core Policies

Products cannot violate any laws

Do not create or develop games utilizing Riot’s Intellectual Property (IP)

No cryptocurrencies, no blockchain

Products cannot closely resemble Riot’s games or products in style or function

Use the following assets in the development and marketing of your product:

Your must post the following legal boilerplate to your product in a location that is readily visible to players

[Your product] isn't endorsed by Riot Games and doesn't reflect the views or opinions of Riot Games or anyone officially involved in producing or managing Riot Games properties. Riot Games, and all associated properties are trademarks or registered trademarks of Riot Games, Inc.

Product Registration

All products must be registered in, and audited by Riot Games through the Developer Portal

Any new features or changes to a product must be audited through the product’s page in the Developer Portal

Products should use supported services from Riot Games for data ingestion

Developer Safety

Do not use a Production API key to run multiple projects (one product per key)

Make sure that you are using SSL/HTTPS when accessing the APIs so that your API key is kept safe.

Do not include your API key in your code, especially if you plan on distributing a binary

Note that for teams working together on a product, there will be an obvious need to share an API key for your product. Our intention is not to discourage sharing along these lines, but rather sharing with people outside of your organization or who are working on other projects. To properly share an API key within an organization, be sure that your product is owned by a “group” in the Developer Portal, then add additional accounts to that group.