iRacing API Scripts

Scripts for authenticating and processing data from the iRacing Web API

Before Proceeding

Prior to anything run ./auth.sh from the root of the project with a .env file containing the following

IRACING_USERNAME=IRACING_USERNAME_GOES_HERE IRACING_PASSWORD=IRACING_PASSWORD_GOES_HERE

This will then create cookie.txt in the root of the project for the current authentication session by which all other API requests require.

Gathering Subsession IDs

Following authentication the first script to be run is /search-series/main.go at time of writing this will require all permutations of season_quarter, season_year and cust_id parameters to be set as an object within /search-series/customer-id-season-quarter-season-year-mappings.json. This will create the input file(s) that depending on how they are being used will need to be merged or used individually within /subsession/main.go.

Gathering Subsession Data

Following runs of /search-series/main.go for all season_quarter, season_year and cust_id permutations next we will be using the output file(s) and using them as the input file for /subsession/main.go the file output here will be used here during the seeding process to Astro DB.

Gathering Past Seasons Data

Following runs of /search-series/main.go for all season_quarter, season_year and cust_id permutations next we will be using the output file(s) and using them as the input file for /past-seasons/main.go as each result in the files has the series_id for each series participated in, these series_id values are to be gathered running /utils/distinct-ids/main.go for all subsessions exported and then saved within /past-seasons as distinct-series-ids-output.json, the search-series results will additionally have the season_id for each series which can be used as seasonIds within this assuming they're mapped to an array and constructed as a unique set like so:

  new Set(series.map((series) => series.season_id))

Gathering Standings Data

Following runs of /search-series/main.go for all season_quarter, season_year and cust_id permutations next will be using the output file(s) and using them as the input file for /standings-jake/main.go or /standings-other/main.go respectively. As each result in the files has the season_id and car_class_id for each series participated in. The file output here will be used here to load standings data into Astro DB via seeding.

Loading Other Data

The following use direct iRacing API responses and simply upload them to a respective Astro DB table:

• This Uses the response from here (/data/carclass/get).
• This Uses the response from here (/data/car/get).
• This Uses the response from here (/data/series/seasons).
• This Uses the response from here (/data/member/info).

/data/member/info Needs to be run by the user the information is for and therefore requires the user to authenticate against the API to get their own user information.

/data/carclass/get, /data/car/get and /data/series/seasons should be run at the start of a subsequent season in order to get the most update to date information regarding each, the last of which (/data/series/seasons) is crucial as this changes every quarterly iRacing season and needs to be pulled prior to the season ending and is what is used for the scheduling portion of Stat 'n' Track.