Valorantapi.py

Latest version: v0.2.1

Safety actively analyzes 688365 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 6

1.5.3

- Fixes some issues while using the leaderboard endpoint which resulted in a 500 error code

tracker.gg Endpoint Replacments
[Tracker] /valorant/v1/match/{match-id} ==> [Ingame] /valorant/v2/match/{match-id}
[Tracker] /valorant/v1/rank/{name}/{tag} ==> [Ingame] /valorant/v2/mmr/{region}/{name}/{tag}

Replacements for the profile and matches Endpoints
I'm working on it, the current limit are the rate limits from the Ingame API, istarted to day to address this issue, see some more information at the next paragraph.

Capacity expansion
I started this morning with the expansion of the Ingame API by creating more Accounts and create a own instance for each of the accounts. I also started with creating a simple routing system, so that if instance one is limited, it reroutes the request to instance two and so on. At the weekend i will work on load balancing between the instances and add more Accounts so that we have 10 instances at the end of that weekend that we can work with to eliminate the main issue. You will be also able to select one instance for whatever reason in the future.

Bot Requests
I experienced over the last week multiple Bot requests at the mmr/by-puuid Endpoint, with the help of CLoudflare and some own Code i blocked the Bots and the bot requests stopped after 2 days. So if you plant to make Bot Requests too that will exceed your rate limits, have in mind that you probably get banned from the API :D

Friend Request failing
I am aware of the problem that some friend requests are failing which causes the complete endpoint to fail, i will take a look at this in the following days.

1.5.2

Take down of the tracker.gg Endpoints

I was friendly asked to take down the Tracker.gg Endpoints because i have no rights to do webscraping their data, which is obviously right, so to prevent any legal issues i have taken down these Endponits, i'm really sorry

1.5.1

Updated Endpoint
- Added new Endpoint /valorant/v2/match
- Includes Detailed Usage of Ablilitys
- Includes Death Locations, Player Locations and Spike Plant Locations
- Includes every single Damage and Kill Event

==> Recreating of the Ingame Match Overview possible

- Added Episode 2 Act 2 as filters to the profile and MMR Endpoint

Fixed
- Fixed that a /valorant/v2/profile request would result in a 504 error when using a filter for season where the user has not played
- Fixed that /valorant/v2/mmr has an empty Act Rank History for some seasons

Other stuff
- Added all changes to the docs

1.5

Updated Endpoint

- Added new Endpoint /valorant/v2/mmr
- Includes MMR History for previous Seasons
- Includes your Act Rank Wins
- Following filter available: e2a1, e1a3, e1a2, e1a1
- Usage: /valorant/v2/mmr/{region}/{name}/{tag}?filter=FILTER-HERE

Other things
- Stabilized /valorant/v1/live-matche ==> Out of Beta
- Regulated 502, 503, 504 to a maximum of 3 of these errors before it fixes itself by logout and login to the client again

1.4.3

Fixed

- Fixed v1/matches endpoint and updated to the new Tracker Structure
- Fixed that filter for that endpoint result in 404, User not found

1.4.2

Added new endpoint [BETA]:

- /valorant/v1/live-match/{name}/{tag}

Important / Note
To make this endpoint work, the requested user have to accept the Bots Ingame Friend Request. So you can't get the presence and live match status of any random user

Error 502-504
I now **try** to automatically logout and login again on Riot Games to reduce the amount of 502-504 errors, we will see how good it work

Page 4 of 6

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.