Indy Lights v2
Quick Access | |
Postman Collection | XSD Schema |
Download |
API | API Version |
Indy Lights | v2 |
Note: Authentication is required for all API calls. |
Example:
>To find the profile for a given racer: >- Call the Seasons endpoint and find the Stage Id for the current season
- Call the Stage Schedule using the 'season' Stage Id
- Locate the Stage Id which your race competed in
- Call the Stage Summary using the 'race' Stage Id
- Within the results locate the competitor id for your racer
- Call the Competitor Profile endpoint using your racer's competitor id
TTL / Cache: | 300 seconds | ||
Update Frequency: | As Necessary | ||
Content Type: | XML or JSON | ||
Mappings Info Data Points: | Name | Merged Id | Retained Id |
English is the only fully supported language for this API. Click here for a tabular list of available languages per competition. | | `format` | xml or json. | | `your_api_key` | Your API key. | Return to top ## Competitor Profile Provides biographical information for a given driver.
TTL / Cache: | 300 seconds | ||
Update Frequency: | As Necessary | ||
Content Type: | Raw XML or JSON | ||
Competitor Information Data Points: | Gender | Id | Name |
English is the only fully supported language for this API. Click here for a tabular list of available languages per competition. | | `competitor_id` | Id of a given competitor. | | `format` | xml or json. | | `your_api_key` | Your API key. | Return to top ## Deleted Stages Provides all deleted stages within a given season.
TTL / Cache: | 300 seconds | ||
Update Frequency: | As Necessary | ||
Content Type: | Raw XML or JSON | ||
Stage Information Data Points: | Description Disabled Scheduled |
Scheduled End Stage Id |
Status Type Unique Stage Id |
English is the only fully supported language for this API. Click here for a tabular list of available languages per competition. | | `stage_id` | Id of a given stage. | | `format` | xml or json. | | `your_api_key` | Your API key. | Return to top ## Seasons Provides a complete historical list of available seasons. This is the starting point for the Indy Lights API.
TTL / Cache: | 300 seconds | ||
Update Frequency: | As Necessary | ||
Content Type: | Raw XML or JSON | ||
Category & Sport Information Data Points: | Category Id Category Name |
Sport Id | Sport Name |
Stage Information Data Points: | Description Disabled Scheduled |
Scheduled End Single Event |
Stage Id Type |
English is the only fully supported language for this API. Click here for a tabular list of available languages per competition. | | `format` | xml or json. | | `your_api_key` | Your API key. | Return to top ## Stage Schedule Provides the schedule for a given stage.
TTL / Cache: | 300 seconds | ||
Update Frequency: | As Necessary | ||
Content Type: | Raw XML or JSON | ||
Category & Sport Information Data Points: | Category Id Category Name |
Sport Id | Sport Name |
Stage Information Data Points: | Circuit Description Disabled |
Scheduled Scheduled End Single Event |
Stage Id Status Type Unique Stage Id |
Venue Information Data Points: | City Coordinates Country Country Code |
Curves Left Curves Right Debut Id |
Length Name Official URL Timezone |
English is the only fully supported language for this API. Click here for a tabular list of available languages per competition. | | `stage_id` | Id of a given stage. | | `format` | xml or json. | | `your_api_key` | Your API key. | Return to top ## Stage Summary Provides schedules and results information based on the stage provided (season, event, practice, qualifying, or race).
Note: Results returned in a Summary endpoint will vary depending on the type of stage provided (season, event, practice, qualifying, qualifying part, or race). View our extended documentation for details or open the links in the right sidebar for samples. |
TTL / Cache: | 300 seconds | ||
Update Frequency: | As Necessary | ||
Content Type: | Raw XML or JSON | ||
Category & Sport Information Data Points: | Category Id Category Name |
Sport Id | Sport Name |
Competitor Information Data Points: | Gender | Id | Name |
Stage Information Data Points: | Description Disabled Scheduled |
Scheduled End Single Event |
Stage Id Type Unique Stage Id |
Results Information Data Points: | Best Speed Car Number Fastest Lap Time Gap/Time Grid Laps |
Podiums Points Pole Positions Position Races Races with Points |
Speed Status Top 10 Top 5 Victories |
Venue Information Data Points: | City Coordinates Country Country Code |
Curves Left Curves Right Debut Id |
Length Name Official URL Timezone |
English is the only fully supported language for this API. Click here for a tabular list of available languages per competition. | | `stage_id` | Id of a given stage. | | `format` | xml or json. | | `your_api_key` | Your API key. | Return to top ## Frequently Asked Questions
Q: How does the stage system work?
A: The Indy Lights API uses generic stage implementation. The core of the API is built around the concept of stages. For example, an event contains the following stage types: practice, qualifying, and race. Each of those stages, in turn, have stages (except Practice which has no sub-stages). The IDs of each stage are usable in the URL path to request information about that particular stage.
The Indy Lights sport and seasons within it are stages as well. The sport stage consists of season stages for each annual season. Using the ID of a chosen season as a parameter in the Stage Summary endpoint you can "drill down" into each season. For example, using the 2022 season ID as a parameter in the Stage Summary endpoint, the sub-stages will be individual race events. From the race event, you can drill down into the practice, qualifying, and race stages using the same endpoint with different stage IDs.
The best way to 'start' the navigation with the Indy Lights API is using the Seasons endpoint. From there one can obtain the stage ID for the season required and use that as a parameter in the Stage Summary endpoint.
Stage Type | Information Included | Sub-stages |
---|---|---|
Sport | Information about the seasons included. Note probabilities do not return valid data on this stage. | Indy Lights seasons. |
Season | Contains the season schedule, driver standings and statistics. | Events on the race calendar for that season. |
Event | Information about a single event, the competitors, the teams, and the circuit. | Sessions (eg: Practice, Qualifying, Race) |
Practice | Competitors and results of practice such as fastest time etc. | None |
Qualifying | Information pertaining to the qualifying stage of the event including conditions, competitors, and overall qualifying results. | Qualifying Parts |
Race | Details of the race itself, including the competitors and overall results. | Laps |
Q: What is the Date format?
A: We present date only values in the ISO 8601 standard format.
ex: 2013-04-03
We use these for attributes that have date and no time (such as birthdate). For more information: https://en.wikipedia.org/wiki/ISO_8601
Q: What time zone are the date time fields presented in?
A: All of our Date/Time attributes are in UTC, presented in the ISO 8601 standard format.
ex: 2013-04-03T18:15:00+00:00
For more information: https://en.wikipedia.org/wiki/ISO_8601
Q: What races are covered in the Indy Lights API?
A: For a detailed breakdown of races covered, reference our Coverage Matrix.
Q: What are the stage types I can expect to see in the feeds?
A: Here are the Indy Lights stage:
- sport
- season
- event
- practice
- qualifying
- race
Q: How do I know what "stage" I am currently looking at?
A: Each stage has a "stage" element. The stage element has an attribute "type" which displays the stage type. The different valid stage types are listed above.
Q: How do I retrieve information about an individual driver?
A: Use the Competitor Profile endpoint with the required driver's competitor ID. The best place to get the driver's competitor ID is the Stage Summary endpoint, using the season stage ID.
Q: Is it updated in real-time?
A: No, post-event. Meaning results of practice are available after practice session is complete, similarly for qualification sessions and the race itself.
Q: Does this API include Qualifying and Practice sessions?
A: Yes, qualifying and practice sessions are updated post-event.
Q: What are the possible statuses of a race or stage?
A: Here are the possible stage statuses and their definitions:
- Cancelled - The stage is cancelled and will not be taking place
- Closed - The stage is over and we have validated the results
- Completed - The stage is over, but we have not finished data collection and validation
- Finished - The stage is over
- Not Started - The stage has not begun
- Preliminary - The stage is about to begin
- Running - The stage is currently in progress
Q: What unit of measurement is used for lap speed?
A: Beginning in 2023, the unit of measurement will be miles per hour. In previous seasons the data will be in kilometers per hour.
Q: What are the possible result statuses?
A: Here are the possible result statuses:
- Finished
- Out
Q: How do I locate the TTL (Time to Live)/cache on an API endpoint?
A: The cache (in seconds) can be accessed in the returned header information on each RESTful API call, under cache-control
.
ex. cache-control: max-age=1, public, s-maxage=1
or
cache-control: public, must-revalidate, max-age=120
Return to top
Docs Navigation
- Documentation
- Football (American Football)
- Football (Soccer)
- Australian Rules Football
- Baseball
- Basketball
- NBA v8
- NBA v7
- NBA v5
- NBA v4
- WNBA v8
- WNBA v7
- WNBA v4
- WNBA v3
- NBA G League v8
- NBA G League v7
- NBA G League v5
- NCAA Men's Basketball v8
- NCAA Men's Basketball v7
- NCAA Men's Basketball v4
- NCAA Men's Basketball v3
- NCAA Women's Basketball v8
- NCAA Women's Basketball v7
- NCAA Women's Basketball v3
- Global Basketball v2
- Global Basketball v1
- Combat Sports
- Cricket
- Editorial Content
- Golf
- Handball
- Hockey
- Images
- Insights
- Insights User Interface
- NBA Insights v2
- NFL Insights v2
- NHL Insights v2
- MLB Insights v2
- NBA Betting Splits v2
- NHL Betting Splits v2
- MLB Betting Splits v2
- NFL Betting Splits v2
- NCAAFB Betting Splits v2
- NCAAMB Betting Splits v2
- NCAAWB Betting Splits v2
- Soccer Betting Splits v2
- NBA Insights v1
- NHL Insights v1
- MLB Insights v1
- NFL Insights v1
- Odds
- Broadcast Graphics
- Racing
- Rugby
- Tennis
- Widgets
- Baseline Sports Coverage
- Badminton v2
- Badminton v1
- Bandy v2
- Bandy v1
- Beach Soccer v2
- Beach Soccer v1
- Curling v2
- Curling v1
- Cycling v2
- Darts v2
- Darts v1
- Field Hockey v2
- Field Hockey v1
- Floorball v2
- Floorball v1
- Futsal v2
- Futsal v1
- Pesapallo v2
- Pesapallo v1
- Snooker v2
- Snooker v1
- Squash v2
- Squash v1
- Table Tennis v2
- Volleyball (Beach) v2
- Volleyball (Beach) v1
- Volleyball (Indoor) v2
- Volleyball (Indoor) v1
- Waterpolo v2
- Waterpolo v1
- Winter Sports v1