Since the following commit:
a hardcoded list of allowed protocols has been added, ignoring what we have configured in the administration UI:
… leading to any attempt to create a new user API key with
fivem://accept-auth as redirect URI hitting a 403 without any information in
/logs or on the end user’s screen.