iRacing Integration
Racey ships iRacing support today via CSV results import and manual cust_id linking. iRacing OAuth is built; waiting on iRacing to reopen new client signups — when it does, your existing setup migrates with no rebuilds.
Link your iRacing customer ID
Driver opens /settings, pastes their iRacing Customer ID into the iRacing card, and saves. Racey records the manual claim so any imported result rows scored under that cust_id are attributed to the driver — no iRacing OAuth or upstream call required.
Import results after each race
Admin opens the league Results page at /league/<slug>/results, uploads the iRacing-exported CSV, Racey matches finishers to linked drivers by cust_id, flags unmatched rows for manual resolution. Standings update on import.
Roster review (manual today)
Without iRacing OAuth, Racey cannot read a driver’s license class, safety rating, or content ownership. Admins manually review eligibility against iRacing’s public profile before approving registrations. Automatic license/safety/content checks return when iRacing reopens new OAuth client signups.
Why this model
iRacing's OAuth was paused upstream in late 2025. We took the time to build a CSV+identity-linking flow that doesn't depend on it. The result: Racey works with iRacing today, and will work better when OAuth returns — same data model, same UX, no rebuilds on your side.
Coming when iRacing reopens OAuth
- Automatic CSV-free result ingest
- Real-time session telemetry hooks
- Automatic license-class, safety-rating, and content-ownership refresh
- Automatic registration content gating against the linked profile