#riotgamesapi

The last two calls are two fundamental calls in the actual creation/registration of a League of Legend’s tournament. These two calls are:

/tournament/public/v1/provider

and

/tournament/public/v1/tournament

/tournament/public/v1/provider is essentially establishing the hosting structure/entity that will be responsible (the face of) a given tournament.

It takes a “region” and a “url”

The next call is the only Mutator currently openly accessible via the Riot Games® API.

/tournament/public/v1/code/{tournamentCode} : Updates the pick type, map, spectator type, or allowed summoners for a code.

Similar to the /tournament/public/v1/code , this call utilizes input parameters to augment/update tournament information.

Up next is the /tournament/public/v1/code/{tournamentCode} call that accesses a given tournaments details via a tournament code generated by the /tournament/public/v1/code  call.

It returns a TournamentCodeDTO,  which contains the aforementioned.

At last, the final bit of formal documentation for the Riot Games® API.

The tournament-provider section of the API is the first section with functions other than Accessors.

The /tournament/public/v1/code is a call that creates a tournament code for a given hosted tournament. It has 6 Parameters:

The summoner calls are dedicated to accessing player provided (stored) data. There are five calls, each mapped to a specific set of info such as summoner objects, rune and mastery pages and names.

These calls are typically used for validation purposes as noted below:

Individual player’s ranked stats can be retrieved via the stats/by-summoner

calls.

There are two types and they encompass a ton of information regarding how they have performed during a ranked season.

It is important to note that this returns aggregated stats (A sum total).

Here is just some of the data returned.

matchlist is a bit different and utilizes a few different means of accessing data which I believe is worthy of mention. The API provides the following based on passed parameters or inputs.

This API call utilizes two different types of parameters, path and query.

These calls are pretty simple and straight forward.

lol-status is an API call that queries a particular server’s status and is great for finding out when game servers are offline.

The system uses “shards” to determine which servers are running and in what regions.

Cool side note is that this request is not counted towards your rate-limit.

match and matchlist are two calls that utilize the client structures in LoL and are external from the client. These are calls that display a specific players match history and or details of a specific match.