GET /tft/summoner/v1/summoners/by-name/{} → endpoint removal
Deprecated, no date
The provider deprecated the GET /tft/summoner/v1/summoners/by-name/{} endpoint on October 16, 2023, without a shutdown date. The endpoint remains usable for now, but callers are discouraged from relying on it because it will be removed in the future. Once removed, requests to this endpoint will fail.
Calls it hits
GET /tft/summoner/v1/summoners/by-name/{}
What to use instead of these calls
Resolve the Riot ID by calling GET /riot/account/v1/accounts/by-riot-id/{gameName}/{tagLine} on the regional host, then call GET /tft/summoner/v1/summoners/by-puuid/{encryptedPUUID}.
In Riot Games API's words
Although deprecated, they can still be used to convert Summoner Names to PUUID or summonerID. However, we discourage using them as part of your application since they will be removed in the future.
Facts
- API
- Riot Games API
*.api.riotgames.com - Kind
- Endpoint removal
- Announced
- October 16, 2023
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Riot Games API's own pages
Questions
When does this change take effect?
Riot Games API deprecated GET /tft/summoner/v1/summoners/by-name/{} without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Riot Games API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Riot Games API 1
-
No date
GET /lol/summoner/v4/summoners/by-name/{}Endpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.