iRacing
iRacing provides car and track metadata that enriches your analysis with accurate naming and categorization.
What iRacing Provides
B4Racing uses iRacing data for metadata only—names and categories, not telemetry:
| Data Type | Description | Used For |
|---|---|---|
| Cars | Names, categories, classes | Car name resolution |
| Tracks | Names, configurations | Track name resolution |
| Series | Series info | Context |
For telemetry analysis, your iRacing sessions need to be synced to Garage61 first. B4Racing doesn't read iRacing telemetry files directly.
Why This Matters
When you ask "Show me my GT3 sessions at Spa," B4Racing uses iRacing metadata to:
- Know that "Spa" means "Circuit de Spa-Francorchamps"
- Understand which cars are in the GT3 class
- Display proper car and track names in results
Without this metadata, B4Racing would only show raw IDs instead of readable names.
How B4Racing Gets This Data
The iRacing metadata is handled by B4Racing internally. You don't need to configure anything—we maintain updated car and track lists from iRacing's data.
Important: iRacing Authentication Changes
iRacing is removing Legacy Authentication on December 9, 2025. After this date, the iRacing Data API will require OAuth 2.0.
This doesn't affect your ability to use B4Racing—we'll update our metadata integration before this deadline. It only impacts direct iRacing API access.
Comparison with Garage61
| Aspect | iRacing Data | Garage61 |
|---|---|---|
| Type | Metadata only | Full telemetry |
| Provides | Car/track names | Sessions, laps, telemetry |
| Your action | None needed | Connect via OAuth |
For full telemetry analysis, you need Garage61. The iRacing metadata just provides names and categories to make your experience better.