An unofficial Node.js library for interacting with the VALORANT game API, including player data, match history, and competitive leaderboards.
Valorant.js is an unofficial Node.js library that allows developers to programmatically interact with the VALORANT game API. It provides methods to authenticate with Riot Games' services, retrieve player statistics, match history, competitive rankings, and in-game content, enabling the creation of third-party tools and applications for the VALORANT community.
Node.js developers building applications, bots, or tools for the VALORANT ecosystem, such as stat trackers, leaderboard viewers, or personal analytics dashboards.
It simplifies the complex authentication process and API interactions required to access VALORANT data, offering a straightforward, promise-based interface and handling token management, region routing, and versioning automatically.
This is an unofficial NodeJS library for interacting with the VALORANT API used in game.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Handles the complex Riot auth process automatically, including token management and refresh, as shown in the authorize method that abstracts away manual token handling.
Implements a wide range of endpoints from player MMR to competitive leaderboards, detailed in the 'Implemented API Calls' list, covering most common use cases.
Includes a wrapper for RiotClientServices.exe, enabling advanced interactions like intercepting local game requests, which is rare in similar libraries.
Maintainer provides a Discord for help and acknowledges issues like client_version updates, showing engagement and ongoing maintenance.
Relies on reverse-engineered endpoints that can break with game updates, requiring manual client_version updates as admitted in the support section, leading to maintenance overhead.
Requires passing and storing plain username/password, which is insecure compared to OAuth and poses risks for server-side applications if not handled carefully.
The README shows basic error catching but lacks built-in mechanisms for rate limiting or retries, forcing developers to implement their own solutions for robustness.