Reference docs for Racey race operations
Use this page when you need operational detail for league setup, race-day work, integrations, and the role-aware workflows that connect drivers, staff, stewards, and broadcasters.
Start Here
The shortest path for new users by role.
Owners, commissioners, and operators
Create the league, shape the season, manage staff, and run the operating workspace for race night.
Drivers, team members, and new joiners
Find leagues, register for seasons, track performance, and handle protests without getting lost in admin tooling.
Stewards, appeals reviewers, and rules officials
Review incidents consistently, understand blind review, and move cases from submission to ruling.
Broadcasters, commentators, and production staff
Stand up overlays quickly, understand tokenized URLs, and verify what your stream team actually needs on race day.
Race directors and operational staff
Own the schedule, results operations, and handoff between league setup and race execution.
Operational Reference
Use these views when you need to confirm how Racey behaves across race operations, not just learn the basics.
League creation, season setup, scheduling, roster approvals, announcements, and branding.
Admin workflowResults lifecycle, staff boundaries, and the handoff from league setup to event execution.
Race ops workflowProtests, blind review, rulings, appeals, and the decisions that require clear, consistent handling.
Steward workflowPermission matrix, role boundaries, workflows, and troubleshooting in one place.
Open cheat sheetIntegrations
The platform connects several race-day systems; these are the pieces most likely to matter when you go live.
Link drivers by iRacing Customer ID, eligibility checks, CSV import, and the OAuth roadmap.
iRacing setupAPI keys and integration planning for bots or analytics.
API docsWebhook setup, bot invite flow, /setup, slash commands, and linked-account DMs.
Discord guideTokenized overlay URLs, browser-source setup, and real-time race graphics.
Broadcast setupStripe entry fees, plan limits, and which features require Pro or Enterprise.
Pricing and billingLeague directory, events, and the first-touch surfaces new users will judge fastest.
Public directoryFind the right support path
Reference pages should make it clear where to go when a workflow, integration, or operational decision needs more context.
Use when the behavior feels wrong or unclear.
Contact supportReference endpoints, keys, and integration patterns.
API documentationTrack what changed so feedback maps to the right build.
Changelog