jasondilworth56
iRacing Changes December 2025 Releaase
Hi Jason
First of all, thank you for the iracingdataapi. I use it in a wide variety of apps.
I have a question regarding the change that iRacing will be making on December 9
(https://forums.iracing.com/discussion/84226/legacy-authentication-removal-dec-9-2025/p1?new=1).
Are you planning to adapt iracingdataapi to the two possible workflows (authorization code flow, password limited flow)?
For my case I think I will do a client registration, to get the necessary client_id.
I use your library in an app that provides results, leaderboards, etc. for our leagues (www.gridmates.ch).
Thank you in advance for your reply.
Best, Andi
Hi Andi, thanks for the interest!
The latest release does allow for using the tokens through the authorization code flow. I'm currently using that in one of my own projects and it's working fine. The thing that will be out of scope for now, and I can't see a way past it long term, is creation and management of those tokens.
Right now my other project is managing user connections itself, with the various callback pages etc that are necessary, and then managing those tokens to use in iracingdataapi. There's a few gotchas to be found around things like expiries and refresh tokens only being valid once that can be a problem if you're using these tokens in some sort of distributed architecture, and for that reason I think it will always make sense for tokens to be managed outside of this project.
On the password limited flow, I haven't actually explored it yet, but I expect that it will work very similarly – as far as I understand it still generates a token for use, and so if you can generate that token you'll be able to use it in the current latest version (1.3.0).
