Application Process

How to get a production api key

The Policies

The first step before even applying for a production API key should be to read and understand the policies. Every project owner will be expected to have read and understood these policies. Failure to adhere to these policies may result in an indefinite revocation of your access to the Riot Games API.


The Process

Notes

If you have questions specific to your project, you should submit an App Note to get an answer. App Notes are the surest and quickest way to get feedback about your project during any stage of the approval process. If you have any questions about your projects or the application process you can post an App Note and we’ll respond. Even during the conceptual phase, you can always register an app, post an app note, and we’ll respond with our initial impressions.


Unverified

This is the natural state of an application after you’ve submitted all the initial information. At this point your application for a production key is waiting for you to verify your project’s website before being reviewed by a moderator. Feel free to register your app and leave it in the unverified state until it’s completed. You can submit an App Note as you come across questions you might have.


Pending

This is the second stage of an application, after you have verified that you indeed are the owner of the website you have listed for your project. At this point your project is waiting to be seen by our moderators. The pending state is not meant as a long term status. Once your application is pending, a moderator will look at and evaluate your application for a production key. Based on your project’s current state, your application for a production key will either be approved or rejected.


Approved or Rejected

Once your application for a production key is approved or rejected, the status of your application can still be adjusted.

Approved

Even if your application was approved, it is still subject to audits and can later be rejected if your project:

  • Violates policies
  • Violates the Terms of Service
  • Doesn't properly secure your API key
  • Ceases to operate in a functioning state
  • Uses the API, or data gathered from the API, in a way other than your application originally stated
  • Uses its API key to power additional projects (every project must be submitted independently and use its own API key)

Please note, even if you have not changed your application since it was approved, it could still be later rejected as policies, perspectives, and the Terms of Service may evolve. If your application is rejected after it has been approved, then your production key will no longer be valid.

Rejected

Whether your application for a production key was rejected from the start or was approved and later rejected, you will usually be provided with an App Note that will outline why your application was rejected. At this point you are encouraged to continue to work on your project until it no longer conflicts with our policies. Once you have made changes, you can submit an App Note letting us know that you are ready for us to re-review your application for a production key.

The Criteria

Moderators use a multitude of criteria for whether an application gets approved for a production key. The most common reasons why an application is rejected are listed below:


  • The project or project’s website is incomplete
    We need to be able to evaluate your project. If the project is no where near completion we have nothing to base our evaluation on. Similarly, your project must have a homepage that your users can visit to get more information. Most of the time vetting a project consists of seeing how the API and its data is being used by visiting the project’s website.

  • The project does not have a clear usage of the API
    We need to be able to determine how you will be using the API on your site. If we can not make this determination your application will be rejected. If your site has an obscure usage for the API this should be noted in an App Note or clearly stated in the description.

  • The project is in conflict with our policies
    If your project comes into conflict with our policies we might ask that you revise your application. Typically projects that are focused on self-improvement are easier to vet. In a presentation put together by the community team, Riot Sargonas mentioned a website called Ward Score that helps players improve their warding by showing how they "stack up" with other players in the warding department. This is a great example of a self-improvement application that we'd happily and swiftly approve.

  • Your project has a barrier to entry
    If your project’s website is password protected we have no way of evaluating your project. If the website requires users to sign up, even if it is free, please provide a sample login that we can use to evaluate your project. If your project requires an electronic device like a smartphone or iPad, your website should provide sufficient documentation to evaluate your project. Sufficient documentation should contain pictures and descriptions of the working application including inputs from the users and the different outputs that display the data you have collected. The League of Legends Lockscreen website is a great example of the type of documentation that will get your mobile application approved.