Skip to content

[Account] (Feature Request) Automatic approval for Personal API Keys for TFT/Legends of Runeterra. #1041

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
4 tasks done
oisincar opened this issue Feb 3, 2025 · 2 comments

Comments

@oisincar
Copy link

oisincar commented Feb 3, 2025

Account Information
My summoner name is Oiz, on EUW, and I'm a player & now developer.

Issue Description
Personal API Keys are automatically approved for League of Legends, but not other games.

What I've Tried
What steps have you tried to resolve the issue.

  • Log out of the Developer Portal
  • Attempt to log in via "Incognito Mode"
  • Clear your browser cookies
  • Attempt to login via a secondary device (mobile or different computer)

Repro Steps
From Developer Dashboard -> Register Product -> Personal API Key. Select TFT as the game, and click 'apply' note that key goes into 'Approval Pending'.

Repeat steps and select League of Legends as game, note that key gets approved instantly.

Registering a game for League of Legends doesn't let you access other endpoints.

Automatic approval for these keys would be fantastic as spending months swapping out the developer keys (while waiting for approval) is not fun.

@bangingheads
Copy link

Automatic approval was only added for League of Legends as a test, this is not a bug, this would be a feature request.

@oisincar oisincar changed the title [Account] Automatic approval for Personal API Keys doesn't work for TFT/Legends of Runeterra [Account] (Feature Request) Automatic approval for Personal API Keys for TFT/Legends of Runeterra. Feb 3, 2025
@oisincar
Copy link
Author

oisincar commented Feb 3, 2025

Automatic approval was only added for League of Legends as a test, this is not a bug, this would be a feature request.

Fair enough - updated the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants