Whitelabel and enterprise setup

Some clubs run DistantRace on a whitelabel deployment: a branded participant portal on a custom domain, connected to the same organizer console and event data on DistantRace.

Whitelabel is a platform-managed offering. DistantRace enables the club flag, OAuth credentials, themed login pages, custom-domain hosting, and SAML identity providers. Organizers continue to create events and manage participants in the manager console as usual.

Contact DistantRace support to discuss whitelabel for your organization.

What whitelabel enables #

How it fits together #

flowchart LR
  subgraph portal [Branded participant portal]
    SPA[Custom domain SPA]
  end
  subgraph drace [DistantRace platform]
    API["/api/v1/"]
    Auth[OAuth + themed login]
    Console[Manager console]
    SAML[SAML discovery]
  end
  SPA -->|org token — public data| API
  SPA -->|user token — after login| API
  SPA -->|redirect| Auth
  Auth --> SAML
  Console --> API

1. Participant portal — a web app on your domain. It loads public event data with an organization-scoped API token and sends participants to DistantRace OAuth for login.
2. DistantRace auth — handles login codes, OAuth, SAML, and sport-app connections. Themed templates apply when the OAuth request includes your organization context.
3. Manager console — organizers create challenges, competitions, tickets, and marketing on distantrace.com. Changes appear on the branded portal through the API.

Setup (platform-managed) #

DistantRace typically handles:

What organizers configure themselves #

Participant login flows #

Whitelabel portals commonly use OAuth authorization code:

1. Participant clicks Sign in on the branded site.
2. Browser redirects to DistantRace /oauth/authorize/ with your organization's UUID.
3. DistantRace shows a themed login page (email code, passkey, or SAML — depending on club configuration).
4. After authentication, the browser returns to your portal with a code exchanged for access and refresh tokens.
5. The portal calls /api/v1/ with the user token for personal actions (join challenge, sync workouts, update profile).

Email invitation links can auto-log participants in via the redeem-email-token API endpoint when the portal is configured with an org token.

SAML SSO is available for enterprise clubs. Participants enter a work email; DistantRace routes to the correct IdP by domain. See Enterprise SAML and whitelabel login.

API credentials (overview) #

Whitelabel integrations use two credential types:

Both are created and rotated by DistantRace during onboarding. Redirect URIs must match your portal's /auth/callback path on each environment (staging *.wl.distantrace.com and production custom domain).

OAuth authorize URL #

Participant sign-in starts at /oauth/authorize/ with:

• client_id — your user OAuth application
• redirect_uri — registered callback on your portal
• response_type=code
• org=<club-uuid> — binds the login page to your organization and selects the themed template

After the participant authenticates (email code, passkey, or SAML), DistantRace redirects to your callback with an authorization code. Exchange it server-side or in the SPA for access and refresh tokens.

Join codes and invitation emails #

Magic-link redemption can auto-create an account from join-code prefill data, return OAuth tokens, and auto-enrol the participant in a bound challenge when configured.

Full endpoint map: Public API overview.

Email and notifications #

When SendGrid is connected:

• Login code emails use your org's transactional template and sender address.
• Registration and marketing templates follow the same integration.

Whitelabel clubs can suppress the automated Daily Overview email for step challenges at the organization level (daily_email_disabled) or per challenge.

Mobile app #

The standard DistantRace mobile app remains available. Participants can connect sport apps and sync steps through the app even when they register on a branded web portal. The app is not white-labeled; account data is shared across distantrace.com, the mobile app, and the branded portal.

Organizer access #

Organizers and staff continue to use the manager console at distantrace.com:

• URL pattern: /console/<org-code>/
• Two-factor authentication is required
• SAML may be used for staff login on enterprise clubs, but console access is separate from the participant portal OAuth flow

See How to access the organizer console.

Related #

• Enterprise SAML and whitelabel login — participant sign-in
• Club branding and hero images
• Embed domains for iframes
• Public API overview
• SendGrid