How to handle rate limits with Valorant.js?

The library doesn't include built-in rate limiting; you'll need to implement throttling based on Riot's undocumented limits, potentially by monitoring response headers or adding delays between requests.

Valorant.js vs Python valorant-api – which is better for my project?

Choose based on your tech stack: Valorant.js is ideal for Node.js applications, while Python alternatives like valorant-api offer similar features. Valorant.js has better local client integration but shares the same unofficial risks.

How to get a player's current rank using Valorant.js?

Use the getPlayerMMR method and parse the response, as demonstrated in the example that calculates Elo from tier and progress values, providing rank and movement details.

Is Valorant.js safe to use with my Riot account?

It requires sharing credentials, which risks account security if not handled properly; use it only in trusted environments and consider token caching, but note there's no OAuth support.

How to update the client version when Valorant.js stops working?

Manually set the client_version property as described in the support section, fetching the latest version from valorant-api.com, since the library doesn't auto-update this.

Can Valorant.js fetch real-time match data?

It can retrieve match details via getMatch, but real-time updates aren't built-in; you'd need to poll the API periodically, which may be inefficient and hit rate limits.

Open-Awesome

valorant.js

JavaScriptv1.5.1

An unofficial Node.js library for interacting with the VALORANT game API, including player data, match history, and competitive leaderboards.

GitHub

109 stars15 forks0 contributors

What is valorant.js?

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.

Target Audience

Node.js developers building applications, bots, or tools for the VALORANT ecosystem, such as stat trackers, leaderboard viewers, or personal analytics dashboards.

Value Proposition

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.

Overview

This is an unofficial NodeJS library for interacting with the VALORANT API used in game.

Use Cases

Best For

Building personal VALORANT stat tracking websites
Creating Discord bots that display player ranks and match history
Developing competitive leaderboard applications for specific regions
Automating the retrieval of in-game storefront and wallet data
Integrating VALORANT player data into custom analytics dashboards
Experimenting with local Riot Client API interactions for advanced tooling

Not Ideal For

Projects requiring official, stable API support with guaranteed uptime and documentation from Riot Games
Applications where user authentication must use secure OAuth flows instead of plain username/password storage
High-traffic services needing built-in rate limiting, retry logic, and robust error handling
Developers building multi-game platforms needing a unified API wrapper beyond VALORANT

Pros & Cons

Pros

Simplified Authentication Flow

Handles the complex Riot auth process automatically, including token management and refresh, as shown in the authorize method that abstracts away manual token handling.

Comprehensive API Coverage

Implements a wide range of endpoints from player MMR to competitive leaderboards, detailed in the 'Implemented API Calls' list, covering most common use cases.

Local Client Integration

Includes a wrapper for RiotClientServices.exe, enabling advanced interactions like intercepting local game requests, which is rare in similar libraries.

Active Community Support

Maintainer provides a Discord for help and acknowledges issues like client_version updates, showing engagement and ongoing maintenance.

Cons

Unofficial and Fragile API

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.

Security Risks with Credentials

Requires passing and storing plain username/password, which is insecure compared to OAuth and poses risks for server-side applications if not handled carefully.

Limited Error and Rate Handling

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.

Frequently Asked Questions

Related Projects

Discord.js

A powerful JavaScript library for interacting with the Discord API

Stars26,813

Forks4,069

Last commit23 hours ago

steam

☁️ Python package for interacting with Steam

Stars1,280

Forks183

Last commit2 months ago

SteamUser

Allows interaction with the Steam network via the Steam client protocol

Stars1,118

Forks189

Last commit9 months ago

Steam Community

Interact with various interfaces on Steam Community from Node.js

Stars580

Forks158

Last commit1 month ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub