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