Riot Games Developer Relations
884 posts

Riot Games Developer Relations
@RiotGamesDevRel
Help and feedback for the Riot Games API and other 3rd Party Developer resources. Have questions? Check out https://t.co/a72EmebXVy
Los Angeles, CA Katılım Mart 2015
21 Takip Edilen13.9K Takipçiler
Riot Games Developer Relations retweetledi

We’ve just reenabled the entire Spectator API (including the getCurrentGameInfoByPuuid endpoint) so now everyone should be able to access live game data again.
This may require some time for 3rd party sites to adjust to these changes, but we’ll be working to support them through navigating these adjustments.
We appreciate your patience while we deploy fixes to bring streamer mode more in line with the vision for the feature that would deliver on an experience that’s long been requested.
English

Hi everyone, in coordination with the recent League of Legends anonymity additions some changes are coming to the Riot Games API. We will be deactivating the Spectator-V5 API for League of Legends to prevent third party applications from deanonymizing players. However, the new anonymous modes will not have any impact on post-match APIs such as Match-V5 or leaderboards. For a full list of available APIs check out developer.riotgames.com/apis
English

Hi all, alongside LoL patch 25.17 we are adjusting our developer policies. There are a few specific use cases for LoL apps that will no longer be approved like notifying players of a power spike(e.g. Garen just leveled up to 6), dictating player actions, and tracking enemy ability/summoner spell cooldowns. You can out our full list of policies at developer.riotgames.com/policies/gener….
English
Riot Games Developer Relations retweetledi

Hey everybody, as a follow up to our last announcement about the endpoints being removed, we are going to be completely removing SummonerIDs and AccountIDs from all endpoint payloads on July 7th, 2025. If your app is dependent on them, please take steps to ensure that you can use PUUIDs moving forward.
Also, please make sure to use this endpoint for RSO-related summoner requests: /lol/summoner/v4/summoners/me
English

Hi all, we are removing many endpoints from the Riot API associated with AcountIDs and SummonerIDs on June 20th. Moving forward, please use the PUUID equivalents of these endpoints which are already available!
Endpoints being removed:
/lol/league/v4/entries/by-summoner/{encryptedSummonerId}
/lol/summoner/v4/summoners/by-account/{encryptedAccountId}
/tft/league/v1/entries/by-summoner/{summonerId}
/tft/summoner/v1/summoners/by-account/{encryptedAccountId}
/tft/summoner/v1/summoners/{encryptedSummonerId}
/lol/summoner/v4/summoners/{encryptedSummonerId}
English

Hey everyone, we’ve updated our policy around advertising in Riot games. Third party in-game advertisements are no longer allowed, this includes ads in overlays, during loading screens, and in the Riot Client. If you’re interested in our full list of policies, check out the documentation on our website for more info: developer.riotgames.com/policies/gener…
English

Hi all, match history data for the new Brawl game mode will not be available through Riot's API when it releases. With Brawl being experimental, we are not in a place where this type of game mode can be supported and we believe that winrate-based data would be detrimental to the Brawl player experience for its duration. As a result of this, querying the Riot API for Brawl match data will result in a 403 error.
English

@darkintaqt @Deadly_Guns correct. Our post and policy is speaking to the developers and if they do not follow policy their applications will no longer work for players.
English

@Deadly_Guns @RiotGamesDevRel So the way I interpreted the text is that the platform will get punished, not you as a user. So there should be nothing to worry about
English

To maintain fair play, we’ve updated our policy to prohibit Enemy Ultimate Timers , effective March 13, 2025, 12AM PDT. Third-party apps must remove this feature by then or risk API key deactivation. For more details, see our updated policy: #developer-api-policy_game-integrity" target="_blank" rel="nofollow noopener">developer.riotgames.com/docs/lol#devel…
English

Questions?
support-developer.riotgames.com
English

Hi all, we will be removing the by summoner ID endpoint from clash-V1 with the release of the next LoL patch and replacing it with a by puuid endpoint. Everyone should plan to transition off the summoner ID endpoint prior to us deprecating it.
Old endpoint:
#clash-v1/GET_getPlayersBySummoner" target="_blank" rel="nofollow noopener">developer.riotgames.com/apis#clash-v1/…
New endpoint:
#clash-v1/GET_getPlayersByPUUID" target="_blank" rel="nofollow noopener">developer.riotgames.com/apis#clash-v1/…
English

Hey folks, the RSO issues should now be resolved. If you continue experiencing trouble with this, please let us know on our support site: support-developer.riotgames.com
English

Hi all! We’re excited to share that you can now access custom lobby match history using League of Legends enabled RSO clients. To protect player privacy, you can only get custom match history using RSO clients, NOT your product API key.
Additionally, this comes with a new policy: Third party sites may not publicly display a player's match history from the custom match queue unless the player opts in to share this specifically for League of Legends. Otherwise, a player’s custom match data may only be made available to them using RSO.
If you have any questions about this, feel free to send us a message on our support site: support-developer.riotgames.com
English
