v1.6

Changes

• The API is now able to perform 10x more requests than before, will add more capacity soon
• Switched from express.js to fastify for one part of the server
• Recode of the whole Ingame API Part (2000 Lines of code to 600)

Coming Changes

• Switch from express.js to fastify on the main server
• Recode of the API
• Eventually /profile endpoint

v1.5.6

• Support for Breeze and the new "Replication" mode
• Started API Recode with fastify

v1.5.5

• Added support for a filter option in the leaderboard endpoint with queries (See further infos in #12)
• Fixed some 504 errors

v1.5.4

Reworked / Reenabled Endpoints:

• /valorant/v2/by-puuid/matches/{region}/{puuid} ==> /valorant/v3/by-puuid/matches/{region}/{puuid}
• /valorant/v2/matches/{name}/{tag} ==> /valorant/v3/matches/{region}/{name}/{tag}

Rate Limit

Rate Limits are now 100 Requests in 2 Minutes instead of 200 Requests in 2 Minutes

Issues Fixed

• Fixed that Friendrequests that fails always give back 500 error code. You now get a 404 one when the user is not found and 500 when some critical things happend in my backend. I also reduced the amount of errors of that type in general and hope that i have fixed the issue that the bot was sometimes unable to send an friendrequest too.
• /valorant/v2/match/{id} now support custom games
  ==> Fixed some small issues at that endpoint too

Capacity Expansion

• Currently there are 4 Ingame Instances available for 4x the capacity than before, i will add more instances over time
  ==> When there is more capacity available i will start to create an profile endpoint

Known Issues

• /valorant/v3/matches and /valorant/v3/by-puuid Endpoints need about 10 Seconds when the matches are uncached, which is definitly a bit too long, working on some improvments

v1.5.3 + Some Information to the profile and matches endpoints and the current state

Update 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.

v1.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

v1.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

v1.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

v1.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

v1.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