Client Registration

Client registration is open to all interested parties. Please contact us to get started.

Requests should come from the email address of an iRacing account.

Note

Registration requests may take up to 10 days to be processed.

To register a client, we will require the following data:

Client Name

The name of the client, which will be displayed to users. This should not include derivatives of the name iRacing such as iRacer, iRace, etc…
Client Type

Will it be server-side, a single-page app, mobile, or native?
Developer’s Name

To be displayed to users unless client is only for the Password Limited authentication flow.
Developer’s URL

To be displayed to users unless client is only for the Password Limited authentication flow.

Not required for Password Limited clients.
Developer’s Email

To be displayed to users unless client is only for the Password Limited authentication flow.
Redirect URIs

The list of URIs allowed for redirects when authentication is completed. Query parameters are allowed but there must be no content in the fragment. These must match exactly during the authentication process.

Not required for Password Limited clients.

See the documentation on Redirect URIs for more information.
Audiences

The iRacing.com service with which the client will interact beyond basic authentication, if any. If the client will not make use of any iRacing.com services, this may be omitted.

Tip

For 3rd parties accessing https://members-ng.iracing.com/data, this is always ‘data-server’. No other audiences exist for 3rd parties at this time.

Once the client is created, we will issue the following data for use in the client:

Sample Request for Password Limited Client

Client Name: My League Manager
Client Type: server-side/native/single-page-app
Developer Name: My Racing League Inc.
Developer URL: https://www.myleague.com
Developer Email: developer@example.com
Redirect URIs:
- https://www.myleague.com/oauth/callback
- https://staging.myleague.com/oauth/callback
Audiences: data-server