Hi @NotOfficer and @Luc1412
Sorry for using the issue tracker for this; I sent an email to contact@fortnite-api.com on 2026-08-28 but probably hasn't been seen yet - totally fair for a volunteer project. :)
I'm a solo developer behind Stat Surfer (statsurfer.gg), a new, small Windows companion app for Fortnite players in private beta. Stat Surfer opens the spectated player's FortniteTracker profile with one click; But before opening it on fortnitetracker.com, the app makes exactly one call to your v2/stats/br/v2/{accountId} endpoint to confirm the account exists and whether its stats are public. Low volume, cached, one request per lookup. It prevents us from sending a user to a fortnitetracker.com stats page with no available stats for the user and allows us to message users that the profile was private or the stats are not available.
The problem: the dashboard's only login is the Discord /login flow, and on 2026-08-28 I got myself banned from your server while sorting out phone verification (I moved my phone number between my two Discord accounts (work/personal) the same day and I suspect the anti-alt check kicked both; the retry the next morning showed "invite not accepted"). Honest mistake, and I've stayed away from the server since rather than try anything that looks like evasion.
Would you mind helping me get back on the server? (whichever is easier for you):
- Lift the server ban for the Discord account HolaSoySauce (user ID [DISCORD_USER_ID]) so I can run /login and regenerate the key myself, or
- Regenerate the key for the dashboard account HolaSoySauce (holasoysauce@statsurfer.gg) and send it to that address.
And if there's anything you want from an app that depends on you (attribution wording, a rate limit to stay under, a heads-up when volume changes), say so and I'll do it. I am looking for more beta testers so if you are interested in poking around Stat Surfer early, please let me know.
Thanks for running this and thanks for your time,
- HolaSoySauce, Hola Soy Sauce, LLC
Hi @NotOfficer and @Luc1412
Sorry for using the issue tracker for this; I sent an email to contact@fortnite-api.com on 2026-08-28 but probably hasn't been seen yet - totally fair for a volunteer project. :)
I'm a solo developer behind Stat Surfer (statsurfer.gg), a new, small Windows companion app for Fortnite players in private beta. Stat Surfer opens the spectated player's FortniteTracker profile with one click; But before opening it on fortnitetracker.com, the app makes exactly one call to your v2/stats/br/v2/{accountId} endpoint to confirm the account exists and whether its stats are public. Low volume, cached, one request per lookup. It prevents us from sending a user to a fortnitetracker.com stats page with no available stats for the user and allows us to message users that the profile was private or the stats are not available.
The problem: the dashboard's only login is the Discord /login flow, and on 2026-08-28 I got myself banned from your server while sorting out phone verification (I moved my phone number between my two Discord accounts (work/personal) the same day and I suspect the anti-alt check kicked both; the retry the next morning showed "invite not accepted"). Honest mistake, and I've stayed away from the server since rather than try anything that looks like evasion.
Would you mind helping me get back on the server? (whichever is easier for you):
And if there's anything you want from an app that depends on you (attribution wording, a rate limit to stay under, a heads-up when volume changes), say so and I'll do it. I am looking for more beta testers so if you are interested in poking around Stat Surfer early, please let me know.
Thanks for running this and thanks for your time,