Download the PHP package islem-kms/riot-api without Composer
On this page you can find all versions of the php package islem-kms/riot-api. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download islem-kms/riot-api
More information about islem-kms/riot-api
Files in islem-kms/riot-api
Package riot-api
Short Description Riot League of Legends & DataDragon API wrapper for PHP7 (Reference to Daniel Dolejska (just a fork)
License GPL-3.0-or-later
Homepage https://github.com/islem-kms/riot-api
Informations about the package riot-api
RiotAPI PHP7 wrapper
Version v4.0.1
Table of Contents
- Available versions
- Introduction
- Downloading
- League of Legends API
- Resource versions
- Initializing the library
- Usage example
- Cache providers
- Rate limiting
- Call caching
- Asynchronous requests
- StaticData endpoints
- StaticData linking
- Extensions
- Callback functions
- CLI support
- DataDragon API
Available versions
Versions | API Updates | Library features | Branch |
---|---|---|---|
✔ | ✔ | master | |
❌ | ❌ | v3-dev |
Introduction
Welcome to the RiotAPI PHP7 library repo! The goal of this library is to create easy-to-use library for anyone who might need one. This is fully object oriented API wrapper for League of Legends' API. A small DataDragon API wrapper is also included.
Here are some handy features:
- Rate limit caching and limit exceeding prevention - fully automatic.
- Call caching - enables the library to re-use already fetched data within given timespan - saves time and key's rate limit.
- StaticData endpoints - you can work with StaticData endpoints as if they were never deprecated.
- StaticData linking - library can automatically link related StaticData right into the returned object.
- Custom callbacks - you can set custom function which will be called before or after the request is processed.
- Object extensions - you can implement your own methods to the fetched API objects and enable yourself to use them later to ease of your work.
- CLI supported - usage of this library in console is extremely easy.
- Interim mode support - you are going to be able to use the library the same way whether your key is in
interim mode
or not (meaning you won't need to change anything when you jump to production). - Objects everywhere - API calls return data in special objects, this allows modern IDEs to hint existing properties and methods.
Please, refer mainly to the wiki pages. This file contains only general introduction to library features.
Downloading
The easiest way to download and use this library is via Composer. If you are not using Composer yet, you should start right now!
While having Composer installed on your machine it takes only composer require "dolejska-daniel/riot-api:^4"
command to get the library ready to roll!
For additional information about downloading and initial setup, please see the wiki pages.
League of Legends API
Resource versions
Below you can find table of implemented API resources and the version in which these are currently implemented. Please refer to wiki pages for additional information about endpoints and resources.
Resource | Status |
---|---|
Champion | |
Champion Mastery | |
League | |
League Exp | |
Masteries | |
Match | |
Runes | |
Spectator | |
Static Data | |
Stats | |
Status | |
Summoner | |
TFT League | |
TFT Match | |
TFT Summoner | |
Third Party Code | |
Tournament | |
Tournament Stub |
Initializing the library
How to begin?
And there is a lot more settings that you can set when initializing the library - mainly to enable special features or to amend default behaviour of the library. Please see the wiki pages for complete list of library's settings.
Usage example
Working with LeagueAPI can not be easier, just take a look at how to fetch summoner information based on summoner's name:
..or how to fetch a static champion data:
More usage examples for LeagueAPI can be found here.
Cache providers
Cache providers are responsible for keeping data of static data within instances of the library for easy re-use. This feature is automatically enabled, when any of previously mentioned features is used.
When using this feature, you can set LeagueAPI::SET_CACHE_PROVIDER
to any class, thought it has to be compatible with PSR-6 standard, eg. implement Psr\Cache\CacheItemPoolInterface
interface.
By using LeagueAPI::SET_CACHE_PROVIDER_PARAMS
or LeagueAPI::SET_DD_CACHE_PROVIDER_PARAMS
option, you can pass any data to the cache provider class.
For additional information about cache providers, please see the wiki pages.
Rate limiting
This clever feature will easily prevent exceeding your per key call limits & method limits.
In order to enable this feature, you have to set LeagueAPI::SET_CACHE_RATELIMIT
to true
.
Everything else is completly automatic, so all you need to do is to enable this feature.
For additional information about rate limiting, please see the wiki pages.
Call caching
This feature can prevent unnecessary calls to API within short timespan by temporarily saving fetched data from API and using them as the result data.
In order to enable this feature, you have to set LeagueAPI::SET_CACHE_CALLS
to true
.
You should also provide LeagueAPI::SET_CACHE_CALLS_LENGTH
option to specify cached data lifetime or else default time interval of 60 seconds
will be used.
For additional information about API call caching, please see the wiki pages.
Asynchronous requests
This feature allows request grouping and their asynchronous sending using Guzzle. After request is sent and its response received, user provided callbacks are invoked with received data.
For additional information about asynchronous requests, please see the wiki pages.
StaticData endpoints
These endpoints provide you with easy way to transform StaticData into object instances and easily work with them. They are also supported in numerous DataDragonAPI functions (displaying images).
For additional information about StaticData endpoints, please see the wiki pages.
StaticData linking
This feature allows you to automatically link static data related to your request, any data are managed through DataDragonAPI
.
All the static data will be locally cached, which makes this operation very fast after its initial requests.
Also, any requests made by DataDragonAPI
do not count towards your rate limit.
For additional information about StaticData linking, please see the wiki pages.
Extensions
Using extensions for ApiObject
s is extremely useful tool, allowing implementation of your own methods and logic into the ApiObject
s themselves.
Extensions are enabled by using settings option LeagueAPI::SET_EXTENSIONS
when initializing the library.
For additional information about API object extensions, please see the wiki pages.
Callback functions
Allows you to provide custom functions to be called before and after the actual API request is sent.
Before callbacks have ability to cancel upcomming request - when false
is returned by any callback function, exception Exceptions\RequestException
is raised and request is cancelled.
For additional information about callback functions, please see the wiki pages.
CLI support
You can also use the library in command line environment:
For additional information about CLI support, please see the wiki pages. More usage examples for LeagueAPICLI can be found here.
DataDragon API
How easy is it to work with static images? For instance, to get loading screen art of Orianna?
Source:
Output:
Render:
...a bit of nostalgia?
Source:
Output:
Render:
...or to display icon of champion and its spells based on its object from API?
Source:
Output:
Render:
For more, please see the wiki pages. More usage examples for DataDragonAPI can be found here.
All versions of riot-api with dependencies
guzzlehttp/guzzle Version ^6
symfony/console Version ^4|^5
symfony/cache Version >=4.3.8
psr/cache Version ^1
php Version >=7.1
ext-json Version *