Web Endpoint for "Account Aliases"

[mikareich]

Apart from the already documented local Account Alias Endpoint, there also exsists its counterparting web endpoint. It has a similiar HTTP signature, although there are some differences:

• Diverging API path api.account.riotgames.com/aliases/v1/aliases optionally with a cluster specific tld.
• Auth would be Authorization: Bearer [access_token].
• Possible query params are gameName and tagLine where gameName will fallback to the authorized user.
  • If query params are specifically set: response is an array of matching accounts represented as AccountAliasObject (view below).
  • If query params aren't specifically set: reponse is an array of objects similiar to AccountAliasResponse, but instead of the entry summoner there is change_required: boolean and shadow_gnt: boolean.

It's a very relevant endpoint if you work on a serverless infra because, as far as i know, no other web endpoint is able to provide me with this kind of data.

wdyt?

see also:

DC/Valorant App Developers: message by floaxy

type AccountAliasObject = {
  puuid: string;
  alias: {
    game_name: string;
    tag_line: string;
  };
};

# example request
curl \
  --request GET \
  --url 'https://api.account.riotgames.com/aliases/v1/aliases?gameName=Jett' \
  --header 'Authorization: Bearer [access_token]'