Overview link

The Alt Sports Data APIs are organized around REST. They return JSON-encoded responses and use standard HTTP authentication and response codes. Our APIs deliver schedules of events, historic scores and results, live scores and our own proprietary odds for upcoming events within the category of alternative sports.

Probabilities and Odds link

We generate outcome odds using proprietary mathematical models, automated algorithms and historic performance data. These support our team of expert traders to provide accurate probabilities and finished odds for a wide range of alternative sports markets and their subsequent derivatives.

Data Feeds link

In addition to probabilities and odds, we provide subscription services for other forms of data, including schedules, statuses, scores, results and rankings. The use case for these data is independent of sports betting and trading, though there is overlap in many instances.

If necessary, we have the ability to add data feeds as a means of end user consumption for contests without available streams. Please read about the availability for this within each sport section below, as it is not yet available for all of our offers. Please contact us for more information regarding data feeds and rights to available streams or feeds at contact@altsportsdata.com.

Key Differences link

There are many key differences between the sports we offer and traditional sports betting markets. These will be outlined in detail within each sport section below, as they are also unique between sports. Our goal is to provide the most overarching and normalized structure as possible, while understanding that most of our efforts will be concentrated during the integration process. We are committed to being flexible and accommodating as we enter a longstanding marketplace with new and unique offers.

We have terminology in our APIs that may differ from current industry standards, so we do not consider this vocabulary to be permanent. Where such differences exist, we will do our best to align those terms and phrases throughout the documentation, and update them during the integration process as necessary.

The API documentation for each sport will include:

Description: A brief summary of the sport
Leagues, Tours and Series: A list of all segments within the sport, the typical season duration and event frequency for each, and whether or not we currently offer our services for each
Event (Contest) Formats: Each season typically has competitions throughout, culminating with a winner via rankings points or a playoffs or championship event. We will provide details into these formats to help you understand our unique markets as well as open and closing schedules for betting.
Schema Details: Schema definitions and parameters required or optional for each endpoint.
Code Examples: Endpoint code examples.

API Definitions link

This section defines our parameters and indicates which sport(s) apply to each when they are not universal. We reiterate that terminology is not permanent.

Events: An "Event" is defined here as a match, game or specific segment of a unified tour or series, in which athletes will generally earn points within a rankings system. We may describe an event as a competition or contest throughout our documentation. This is not the same as a single, bettable event, like a proposition or matchup, and we may change this terminology if necessary.
- id: Unique ID related to the contest.
- name: The name of the contest, which may not be unique.
- tourName: The name of the tour or league that is hosting the contest (tour is a general sub-category within a sports league, and may not necessarily apply directly to a tour as defined by the official association).
- startDate: The expected start date for the contest.
- endDate: The expected end date for the contest.
- year: The year in which the season of the contest started (for seasons that span more than a single calendar year, we use only the first year to apply for each contest - for example, if the 2021 Nitro Rallycross season concludes in 2022, the year applied to a contest held in March of 2022 will be 2021, while the endDate will be in 2022).
- eventNumber: The sequential number of the event within the season for that league and year - for example, the first contest of a season will show an eventNumber of 1.
- eventStatus: The status of the contest, to indicate if it is scheduled and upcoming, live, completed, canceled or postponed.
- eventLocation: The geographical location of the contest to the best standardization possible - for example, while we can format contest locations for the United States as City, State, USA, it is not always the same format internationally and we may adapt these formats as necessary.
- eventLocationGroup: (Applies to World Surf League only) This is similar to eventLocation, but denotes a contest lineage that may be held at different geographical locations - for example, the Gold Coast Pro is typically held at Kirra Beach in Coolangatta, Queensland, Australia. However, due to surf conditions, it may be held at another beach in the neighboring city of Tweed Heads, Queensland, Australia. As such, eventLocationGroup will still be the same for both contests, while the eventLocation will be different.
- rounds: A round is the same as any contest segment at the highest level, regardless of whether it is defined as a Round by the official sports organization. It is an array of objects that provide details about the round, as well as further segmentation of the contest formats as applicable.
  - id: Unique ID related to the round segment.
  - roundName: The name of the round segment - for example, Round 1, Qualifying Round or Battle Bracket Final.
  - roundNo: The sequential number of the round segment within the contest, for chronological record.
  - roundStatus: Round statuses are the same as contest or event statuses, and each will be applied to round segments.
  - startDate: The start date of the round segment.
  - endDate: The end date of the round segment.
  - heats: A heat is a segment of a round, and may or may not be labeled as a Heat by the official sports organization.
    - id: Unique ID related to the heat sub-segment.
    - heatName: The name of the heat sub-segment.
    - heatNo: The sequential number of the heat sub-segment within the round segment, for chronological record.
    - heatStatus: Heat statuses are the same as contest or event and round statuses, and each will be applied to the heat sub-segments.
    - startDate: The start date of the round segment.
    - endDate: The end date of the round segment.
    - Get Heat Score: Use eventId and heatId to get heat scores. Heat scores can be scores, lap times, or race times attributed to athletes or teams and is an array of the following:
      - eventId: The ID related to the event
      - heatId: The ID related to the heat
      - athleteRoundSeed: The round seed for an athlete. Round seeds are the ranking for each athlete within a round segment, if the contest format requires it for athlete placement. It is similar to, but often different from, an athlete's event seed.
      - athleteRoundRank: The final position of the athlete after the round segment has ended.
      - athleteHeatScore: An athlete's score for a heat. Applies only to:
        
        World Surf League (WSL)
        
        Street League Skateboarding (SLS)
      - athleteLapTime: An athlete's lap time for a lap within a race. This applies only to the following sports:
        
        Nitro Rallycross (NRX)
        
        AMA Supercross
      - athletePenaltyTime: An athlete's penalty time for a lap within a race This applies only to the following sports:
        
        Nitro Rallycross (NRX)
        
        AMA Supercross
      - athleteLapStatus: The status of the lap. This applies only to the following sports:
        
        Nitro Rallycross (NRX)
      - lapNo: An athlete's sequential lap number for a lap within a race.This applies only to the following sports:
        
        Nitro Rallycross (NRX)
        
        AMA Supercross
      - roundScore: An athlete's score for the round, equal to the sum of the highest three scores out of one Run and four to six individual tricks, all judged out of a maximum of 10 points for a maximum round score of 30 points. It applies only to:
        
        Street League Skateboarding (SLS)
      - runScore: A segment of an athlete's roundScore in Street League Skateboarding that applies to their Run - a series of tricks performed during a timed session, judged out of a maximum of 10 points.
      - trick#Score: A segment of an athlete's roundScore in Street League Skateboarding that applies to one of their multiple, individual tricks. In the Qualifying Round, each athlete has four individual tricks to attempt. In the Final, each athlete has four individual tricks to attempt and after each athlete attempts all four individual tricks, the athletes with the top four round scores each earn an additional two trick attempts for a total of six trick attempts in the Final. Tricks are each judged out of a maximum of 10 points and may contribute to the athlete's roundScore.
      - athlete: The person performing in the sport. This array includes a Unique ID (id), first and last name, nationality, and for World Surf League and Street League Skateboarding, stance. Stance is either Regular (left foot in front) or Goofy (right foot in front) or Switch (either foot can be in front, like a switch-hitter in baseball) on the respective board.
- Get Event Odds: Use eventId and oddType to get odds for markets offered for a contest (event).
  - oddType: The market for which odds will be returned. This list is not finite, nor permanent in structure and is subject to change as new markets are added. The structure and response of the request and response are flexible and can be changed on request.
    Each oddType array includes Unique Odd ID (id), Decimal Probability between 0 and 1 (probability) and the odds, including any pre-agreed margins applied (odds) as well as unique objects defined within each type below:
    - eventWinner: The market for which odds will be returned. This list is not finite, nor permanent in structure. We understand that there are better ways to combine certain fields, or to utilize status instead of separate objects for delivering certain details. However, we await an initial integration to provide clarity on the best path forward for this structuring.
      - position: Indicates the position of the athlete with respect to the odd. This can be the likelihood of an athlete in first place or second place, wherein position will have the value of 1 or 2. Also applies to secondPlace below.
    - secondPlace: Odds for each athlete to place second in the contest, overall.
    - heatWinner: Odds for an athlete to win a heat or grouped matchup against one or more athletes within a heat. This is dependent on the known participants of the heat prior to markets opening.
      - id: The associated, unique ID for the odd.
      - roundId: The associated, unique ID for the round.
      - roundName: The name of the round segment.
      - roundNo: The sequential number of the round segment within a contest, for chronological record.
      - roundStatus: The status of the round segment.
      - heats: An array of heats for which odds are being, or will be, generated, within the round segment.
        
        id: The associated, unique ID for the heat.
        
        name: The name of the heat - for example, Heat 7.
        
        heatNo: The sequential number of the heat segment within a round segment, for chronological record.
        
        heatStatus: The status of the heat segment.
        
        athletes: The status of the heat segment. athletes: The identifying and biographical objects for each athlete participating in the heat, as well as:
        
        probability: The probability between 0 and 1 for the athlete to win the heat against the other known heat athletes.
        
        odds: The translated probability as well as any pre-agreed margin as odds for the athlete to win the heat against the other known heat athletes
        
        seedNo: The athlete's round seed number, which is used to determine their placement into the heat by the contest format.
    - headToHead: Odds for one athlete to finish the contest in a better overall position than another athlete. This is a matchup for formats that may not typically have head to head formats during any contest segment. We understand that the structure here, as in other responses, may not seem ideal. We will align our data with the endpoints of our initial integrated client, and do not consider these structures as permanent.
      - eventParticipant#: The athlete, their odds to win the head to head matchup versus the other athlete, and their final contest position if the contest is “Completed” (as a verification method).
      - winnerParticipantId: The athlete ID of the winning athlete. This structure will change during the initial integration process to meet client formatting.
      - betStatus: Indicates whether the market should be paid to no bettors, and is voided by the trader for any reason or if it should be paid to bettors of the winning athlete or if the market resulted in a draw between the two athletes. It is intended as an indication along with a note, as each client may have different rules regarding how they govern head to head ties for their players.
    - propBets: Odds for any various number of propositions that are not considered standardized toplines or derivatives. Props may or may not be tied to an individual athlete.
      - proposition: A string that describes the proposition from the Trader - for example: “Athlete A will complete at least two tricks during the Qualifying Round run.”
      - odds and probability: Over/Unders will be included in the odds package for propBets following an initial integration process.
    - shows: Odds for one athlete to finish the contest in either first or second place.
    - podiums: Odds for one athlete to finish the contest in either first, second or third place.

Sports

Surfing link

Surfing is a judged sport where athletes ride boards on ocean or man-made waves to earn the highest possible score, based on judging criteria. World Champions are determined by a final event or playoff, where the top overall ranked athletes are seeded every year.

Leagues, Tours and Series link

The World Surf League is the only surfing league we offer at this time. The table below shows the name of each tour that exists, when the typical season runs, how many events a season will host on average, and how many markets we can produce per event, on average. We currently offer Men’s and Women’s Championship tours, with plans to offer Big Wave Tours next, due to high consumption rates compared to other tours.

League	Tour	Season	Contests	Markets per Contest	Offer Status
World Surf League	Men’s Championship Tour	Jan - Sep	11	30 - 50	Offered
	Women’s Championship Tour	Jan - Sep	11	20 - 30	Offered
	Men’s Big Wave Tour	Feb - Mar	3		Planned
	Women’s Big Wave Tour	Nov - Mar	1		Planned

Contest Formats link

3-athlete heats are used in two qualifying rounds (Opening Round and Elimination Round) to seed the main event bracket. Once the main event is seeded, 2-athlete heats (head-to-head) are run in a linear progression until a winner is determined.

Regardless of how many athletes are in a heat, the highest heat score wins. Heat score is the sum of the athlete’s 2 highest individual wave scores, out of a maximum of 10.00 (meaning, the maximum heat score is 20.00). The winners advance until an event winner is determined.

Surfing events have distinct states after Upcoming. Each event reserves a 10-14 day window in which to run the competition (what we consider “Live” status). Within that window, if an event is not actually happening, the status is “In-Window” since it can then be “Live” at any point. Once the official horn sounds for the first heat of the day, the event status is “Live” until the final heat ends.

Heats are typically 30 to 45 minutes in length, and are run consecutively until the “Live” period is completed. Our traders will use this long period between heat starts to utilize scheduling functions within their interface to either automate, or manually select the next heat start time.

Markets and Wagering Times link

Our trading team uploads and maintains the event schedules for all tours offered for Surfing. As mentioned in the previous section, these known date ranges are In-Window, and Live status will only be known each day.

Event Trading Lifecycle:

Upload Schedule
Event status moves to “Upcoming” (pre-match)
1. Trader uploads Event Seeds and Base Projections to event
2. Trader maintains Event Seeds list against any athlete withdrawals or replacements until event status becomes “In-Window”
3. Wagering may open for Futures; can be up to 1 month before event window
Event Status moves to “In-Window”
1. Competition can now become “Live” at any time
2. Trader starts first heat in sync with the live broadcast, or does not if the contest is determined to be on hold for the day due to surf conditions
3. Wagering may open for Futures and Round 1 heat winners; can be up to 1 week before competition begins
Event Status moves to “Live”
1. The call is made to start the first heat of the event at a specified time. The trader sets this in the trader interface for Heat 1
2. The call is made to start the first heat of the event immediately, the trader selects to start the heat now in the trader interface for Heat 1.
3. Wagering on the first iteration of Futures closes
4. Wagering on Heat 1 matchup closes; the rest of the heat matchups remain open for betting and Futures are updated using the results of Heat 1 to their second iteration
The first heat ends
1. The trader has input the heat scores for each athlete, saves, confirms and “Ends Heat” in the trader interface
2. Depending on their prior set interaction with the next consecutive heat, the End Heat function may automatically send an end timestamp for the current heat and a start timestamp for the next heat.
3. If the next heat has been set to automatically start, betting for it will be closed, but remain open for the rest of the upcoming heats.
4. If the next heat has been set to start in the future, betting will remain open for it and the event status will move back to “In-Window” until that time.

API Integration

All of our API endpoints can be accessed via an HTTP request using your API key. The API key can be passed using the following HTTP request header.
X-API-KEY: {key}

Here is a link to detailed documentation and a link to try it for yourself.

Schema Details and Response Samples

Fetch Surfing Events

View API


  [
    {
      "id": "wsl:2127ea10-6110-4ffd-9403-3e33fc0929de",
      "name": "Billabong Pipe Masters",
      "tourName": "World Surf League",
      "startDate": "2022-01-29T13:00:00Z",
      "endDate": "2022-02-10T19:00:00Z",
      "year": 2022,
      "eventNumber": 11,
      "eventStatus": "COMPLETED",
      "eventLocation": "Banzai Pipeline, Oahu, United States",
      "eventLocationGroup": "Pipeline"
    }
  ]

Fetch Surfing Event Winner Odds

View API


  {
    "eventId": "wsl:636d414b-8d24-49d2-a9d8-57ec650a4e0e",
    "oddType": "eventWinner",
    "eventWinner": [
      {
        "id": "636d414b-8d24-49d2-a9d8-57ec650a4e0e",
        "position": 1,
        "probability": 0.6,
        "odds": 1.344,
        "athlete": {
          "id": "636d414b-8d24-49d2-a9d8-57ec650a4e0e",
          "firstName": "Filipe",
          "middleName": "",
          "lastName": "Toledo",
          "nationality": "BRA",
          "stance": "Regular"
        }
      }
    ]
  }

Skateboarding link

Skateboarding is a judged sport where athletes ride boards on street style courses or man-made ramps to earn the highest possible score, based on judging criteria.

World Champions are determined by a final event, where the top overall ranked athletes are seeded every year.

Leagues, Tours and Series link

Street League Skateboarding is the only skateboarding league we offer at this time. The table below shows the name of each tour that exists, when the typical season runs, how many contests a season will host on average, and how many markets we can produce per contest, on average. We currently offer Men’s and Women’s Championship tours, with plans to offer Big Wave Tours next, due to high consumption rates compared to other tours.

League	Tour	Season	Contests	Markets per Contest	Offer Status
Street League Skateboarding	Men’s Championship Tour	Apr - Nov	4	15 - 20	Offered
Street League Skateboarding	Women’s Championship Tour	Apr - Nov	4	10 - 20	Offered

Contest Formats link

Heats of up to 6 athletes are used in one Qualifying Round to seed the Final Round. Once the Final Round is seeded, one heat is run, resulting in the final event leaderboard and final athlete places.

Regardless of which heat an athlete skates in, their round score from the Qualifying Round is ranked among all other athletes in an overall leaderboard. Round score is the sum of the athlete’s 3 highest individual scores, out of a maximum of 10.00, for a maximum potential round score of 30.00.

In a heat, each athlete skates a timed run for their first judged score. They can skate any part of the park and freestyle any number of tricks within the time allowed. Each athlete then alternates to perform 4 individual tricks, each earning an additional judged score. These 5 scoring attempts are the pool of scores from which their highest 3 are combined for their total round score. The top 8 athletes after the Qualifying Round advance to the Final Round, where after each athlete’s fourth trick attempt, the top four earn another two trick attempts to improve their score.

Event states include “Next” (similar to Upcoming, but an extra indication to note that it is the next chronological event in the schedule that has not started yet), “Upcoming” (scheduled for a future date, and not the next event chronologically), “In-Window” (between the start and end date time, but not Live competition), “Live” (competition is happening and the broadcast is live”), and “Completed” once the final heat has ended and the contest is over.

Heats are run consecutively until the “Live” period is completed. Our traders will use this long period between heat starts to utilize scheduling functions within their interface to either automate, or manually select the next heat start time.

Markets and Wagering Times link

Our trading team uploads and maintains the event schedules for all tours offered for Skateboarding. As mentioned in the previous section, these known date ranges are In-Window, and Live status will be scheduled.

Event Trading Lifecycle:

Upload Schedule
Event status moves to “Upcoming” or “Next” (pre-match)
1. Trader uploads Event Seeds and Base Projections to event
2. Trader maintains Event Seeds list against any athlete withdrawals or replacements until event status becomes “In-Window” and then subsequently, “Live”
3. Wagering may open for Futures, potentially up to 1 year before event window
Event Status moves to “In-Window”
1. Competition can now become “Live” at any time
2. Trader starts first heat in sync with the live broadcast, which may be on the scheduled time or not
3. Wagering may open for Futures and Qualifying Round heat winners; potentially up to 1 year before competition begins
Event Status moves to “Live”
1. The trader confirms the start time in the trader interface for Heat 1
2. Wagering on the first iteration of Futures closes
3. Wagering on the first iteration of Futures closes
4. Wagering on Heat 1 matchup closes; the rest of the heat matchups remain open for betting, and Futures are updated using the results of Heat 1 to their second iteration
The first heat ends
1. The trader has input the individual scores for each athlete, saves, confirms and “Ends Heat” in the trader interface
2. Depending on their prior set interaction with the next consecutive heat, the End Heat function may automatically send an end timestamp for the current heat and a start timestamp for the next heat.
3. If the next heat has been set to automatically start, betting for it will be closed, but remain open for the rest of the upcoming heats.
4. If the next heat has been set to start in the future, betting will remain open for it and the event status will move back to “In-Window” until that time.

API Integration

All of our API endpoints can be accessed via an HTTP request using your API key. The API key can be passed using the following HTTP request header.
X-API-KEY: {key}

The API for each sport has been separated by adding a sport identifier to the API path. For instance, all Skateboarding APIs reside under /api/v1/sls/*.

Here is a link to detailed documentation and a link to try it for yourself.

Schema Details and Response Samples

Fetch Skateboarding Events

View API

          
  [
    {
      "id": "sls:2127ea10-6110-4ffd-9403-3e33fc0929de",
      "name": "SLS Salt Lake City",
      "tourName": "Women's Street League Skateboarding",
      "startDate": "2021-08-27T10:00:00Z",
      "endDate": "2021-08-28T18:00:00Z",
      "year": 2021,
      "eventNumber": 1,
      "eventStatus": "COMPLETED",
      "eventLocation": "Salt Lake City, Utah, USA",
      "eventLocationGroup": "Salt Lake City, Utah, USA",
    }
  ]

Fetch Skateboarding Event Winner Odds

View API

          
  {
    "eventId": "sls:636d414b-8d24-49d2-a9d8-57ec650a4e0e",
    "oddType": "eventWinner",
    "eventWinner": [
      {
        "id": "636d414b-8d24-49d2-a9d8-57ec650a4e0e",
        "position": 1,
        "probability": 0.6,
        "odds": 1.344,
        "athlete": {
          "id": "636d414b-8d24-49d2-a9d8-57ec650a4e0e",
          "firstName": "Rayssa",
          "middleName": "",
          "lastName": "Leal",
          "nationality": "BRA",
          "stance": ""
        }
      }
    ]
  }

Nitro Rallycross link

Nitro Rallycross is a motor racing sport where athletes drive specialized cars on architected tracks to advance throughout a contest with the fastest lap and race times.

World Champions are determined by the highest total rankings points for the season.

Leagues, Tours and Series link

The table below shows the name of each tour that exists for Nitro Rallycross, when the typical season runs, how many events a season will host on average, and how many markets we can produce per event, on average. We currently offer the top class tour of Group E (Electric) only. Group E has completely replaced Supercar, which no longer exists.

League	Tour	Season	Contests	Markets per Contest	Offer Status
Group E	Jul - Mar	10	148 - 306	Offered
Nitro Rallycross	Supercar				No longer exists.
	Next	Jul - Mar	10		Not Offered
	CrossCar	Jul - Mar	10		Not Offered

Contest Formats link

A Timed Qualifying Lap and subsequent Battle Qualifying Heat Races determine the seed list for a head-to-head Battle bracket of 16 total athletes. Athletes race each other head-to-head, with the first driver across the finish line after 3 total laps winning the Battle. One of the 3 laps must be through a different part of the course called the Joker lap (though in some instances this rule is changed to accommodate track conditions, and the Joker may not always be used). If in play, the athletes must take the Joker lap route once, and only once, during their 3-lap Battle. It is up to the athlete to decide when to take their single Joker lap during the race.

Once the Battle bracket is completed, the athletes advance as seeds into heat races (more than 2 athletes per race). 1st and 2nd place from the Battle bracket are seeded 1 and 2 into heat races, while the rest of the equal finishing places among Battle bracket participants are sub-seeded by their initial Solo Qualifying Lap time.

Heats Round 1 consists of 2 heats of 8 athletes each (as opposed to head-to-head format of the Battle races). Seeds are alternated between the heats, with the higher seeds awarded pole and primary grid starting positions. Heats Round 1 races are 5 laps in total, and each athlete must take one, and only one, Joker lap during the race. It is up to the athlete to decide when to take their single Joker lap during the race.

Athletes who finish their Heats Round 1 heat in 1st or 2nd place (4 athletes total) advance directly to the Final race. The rest of the athletes are seeded, based on Heats Round 1 heat place, into the Heats Semifinal.

The Semifinal consists of 2 heats of 6 athletes each. They are 5 laps with 1 one the 5 required to be a Joker lap per athlete. Like all other races in the contest, the athlete’s place is determined by their total race time, with the fastest time being the winner.

Athletes who finish 1st or 2nd in their Semifinal heat (4 total athletes) advance to the Final race to be seeded lower than the Heats Round 1 heats winners, in order of Semifinal heat finishing place. Athletes who finish 3rd or worse in their Semifinal heat advance to the Last Chance Qualifier race.

The Last Chance Qualifier race consists of 1 heat of 8 athletes. It is 3 laps with 1 of the 3 laps required to be a Joker lap per athlete. The top 2 finishing athletes advance to the Final race. The rest of the athletes are eliminated and their final event place is determined by their Last Chance Qualifier heat place.

The Final race consists of a single heat of the 10 aforementioned athletes. The final heat place of each athlete is the overall event place for the contest. Races are 6 laps with 1 of the 6 required to be a Joker lap per athlete.

Throughout the contest, penalties may be applied by officials for rule violations. These can be additions of time to race times (which may impact the result of a race or contest), or disqualifications. Alt Sports Data will wait to confirm finality of all results, regardless of officially recorded lap times by the on-site systems, to settle bets and close markets.

Markets and Wagering Times link

Nitro Rallycross provides official scheduling, timing, contest and athlete data directly to Alt Sports Data via realtime API. This is supplemented by our trading team, who monitor and interact with the competition data for quality assurance.

Event Trading Lifecycle:

Upload Schedule
Event status moves to “Upcoming” or “Next” (pre-match)
1. Alt Sports Data receives participant list via official API, and trader uploads Base Projections for each participating athlete. Participants list can be overwritten by the API when changes are made before the contest.
2. Trader maintains Event Seeds list against any athlete withdrawals or replacements until event status becomes “In-Window” and then subsequently, “Live”
3. Wagering may open for Futures
Event Status moves to “In-Window”
1. Competition can now become “Live” at the scheduled time
2. API data triggers event Live status, which is confirmed by the trader
3. Wagering may open for Solo Qualifying Lap, and all other events following confirmation of seed list for Battle bracket, including Battle bracket matchups
Event Status moves to “Live”
1. The trader confirms the start time in the trader interface, which is triggered by official API data.
2. Wagering on the first iteration of Futures closes.
3. Wagering on Solo Qualifying Lap closes.
Solo Qualifying Lap ends
1. The API delivers final lap times to Alt Sports Data, and the trader confirms any penalties applied, along with the final results
2. The trader settles bets as appropriate
3. The Battle bracket is now seeded and odds are generated
4. Wagering is open for Battle bracket
Battle Bracket battle 1 starts
1. API data triggers the start of the first Battle in the Battle bracket
2. Wagering for Battle bracket Battle 1 closes, while all other battles in the first battle round remain open
3. API delivers results and end-time, trader confirms and settles or voids bets as appropriate
Battle Brackets battle 2 starts
1. From here forward, the same open and close of wagering applies to battles, heats or races that start via API trigger
2. All results are confirmed by a trader before being settled or voided as appropriate

Markets

We offer standard markets for Futures, with realtime updates as a contest progresses. We also offer multiple markets and props.

Example Futures:

Athlete A wins contest overall (first place overall)
Athlete podiums (finishes first, second or third place overall)
Fastest Joker Lap Time overall
Fastest race time overall over/under

Example Matchups:

Athlete A places better in the event overall than Athlete B
Athlete C has a better Round Score than Athlete D

Example Props:

Athlete E makes more than 2 trick attempts in the Qualifying Round
Athlete F loses Battle with a faster Joker Lap than opponent
Total board changes in Opening Round over/under

API Integration

All of our API endpoints can be accessed via an HTTP request using your API key. The API key can be passed using the following HTTP request header.
X-API-KEY: {key}

The API for each sport has been separated by adding a sport identifier to the API path. For instance, all Nitro Rallycross APIs reside under /api/v1/nrx/*.

Here is a link to detailed documentation and a link to try it for yourself.

Schema Details and Response Samples

Fetch Nitro Rallycross Events

View API

          
  [
    {
      "id": "nrx:2127ea10-6110-4ffd-9403-3e33fc0929de",
      "name": "Round 2 - Strängnäs",
      "tourName": "Group E",
      "startDate": "2022-07-31T10:00:00Z",
      "endDate": "2022-08-01T12:00:00Z",
      "year": 2012,
      "eventNumber": 2,
      "eventStatus": "COMPLETED",
      "eventLocation": "Strängnäs Motorstadion, Strängnäs, Sweden",
      "eventLocationGroup": "Strängnäs Motorstadion, Strängnäs, Sweden"
    }
  ]

Fetch Nitro Rallycross Event Winner Odds

View API

          
  {
    "eventId": "nrx:2127ea10-6110-4ffd-9403-3e33fc0929de",
    "oddType": "eventWinner",
    "eventWinner": [
      {
        "id": "636d414b-8d24-49d2-a9d8-57ec650a4e0e",
        "position": 1,
        "probability": 0.6,
        "odds": 1.344,
        "athlete": {
          "id": "636d414b-8d24-49d2-a9d8-57ec650a4e0e",
          "firstName": "Fraser",
          "middleName": "",
          "lastName": "MCCONNELL",
          "nationality": "JAM",
          "stance": ""
        }
      }
    ]
  }

Formula 1 link

Formula 1 is the pinnacle of motorsport, featuring the fastest cars, skilled drivers, and cutting-edge technology in a global championship known for its high-speed races and intense competition.

World Champions are determined by the highest total rankings points for the season.

Leagues, Tours and Series link

The table below shows the name of each tour that exists for Formula 1, when the typical season runs, how many events a season will host on average, and how many markets we can produce per event, on average.

League	Tour	Season	Contests	Markets per Contest	Offer Status
Group E	Jul - Mar	10	148 - 306	Offered

Contest Formats link

Markets and Wagering Times link

Event Trading Lifecycle:

Upload Schedule
Event status moves to “Upcoming” or “Next” (pre-match)
1. Alt Sports Data receives participant list via official API, and trader uploads Base Projections for each participating athlete. Participants list can be overwritten by the API when changes are made before the contest.
2. Trader maintains Event Seeds list against any athlete withdrawals or replacements until event status becomes “In-Window” and then subsequently, “Live”
3. Wagering may open for Futures
Event Status moves to “In-Window”
1. Competition can now become “Live” at the scheduled time
2. API data triggers event Live status, which is confirmed by the trader
3. Wagering may open for Solo Qualifying Lap, and all other events following confirmation of seed list for Battle bracket, including Battle bracket matchups
Event Status moves to “Live”
1. The trader confirms the start time in the trader interface, which is triggered by official API data.
2. Wagering on the first iteration of Futures closes.
3. Wagering on Solo Qualifying Lap closes.
Solo Qualifying Lap ends
1. The API delivers final lap times to Alt Sports Data, and the trader confirms any penalties applied, along with the final results
2. The trader settles bets as appropriate
3. The Battle bracket is now seeded and odds are generated
4. Wagering is open for Battle bracket
Battle Bracket battle 1 starts
1. API data triggers the start of the first Battle in the Battle bracket
2. Wagering for Battle bracket Battle 1 closes, while all other battles in the first battle round remain open
3. API delivers results and end-time, trader confirms and settles or voids bets as appropriate
Battle Brackets battle 2 starts
1. From here forward, the same open and close of wagering applies to battles, heats or races that start via API trigger
2. All results are confirmed by a trader before being settled or voided as appropriate

Markets

We offer standard markets for Futures, with realtime updates as a contest progresses. We also offer multiple markets and props.

Example Futures:

Athlete A wins contest overall (first place overall)
Athlete podiums (finishes first, second or third place overall)
Fastest Joker Lap Time overall
Fastest race time overall over/under

Example Matchups:

Athlete A places better in the event overall than Athlete B
Athlete C has a better Round Score than Athlete D

Example Props:

Athlete E makes more than 2 trick attempts in the Qualifying Round
Athlete F loses Battle with a faster Joker Lap than opponent
Total board changes in Opening Round over/under

API Integration

All of our API endpoints can be accessed via an HTTP request using your API key. The API key can be passed using the following HTTP request header.
X-API-KEY: {key}

The API for each sport has been separated by adding a sport identifier to the API path. For instance, all Nitro Rallycross APIs reside under /api/v1/nrx/*.

Here is a link to detailed documentation and a link to try it for yourself.

Schema Details and Response Samples

Fetch Formula 1 Events

View API

                    
            [
              {
                "id": "nrx:2127ea10-6110-4ffd-9403-3e33fc0929de",
                "name": "Rolex Grosser Preis Von Österreich",
                "tourName": "Formula 1",
                "startDate": "2023-06-30T10:00:00Z",
                "endDate": "2023-07-02T12:00:00Z",
                "year": 2023,
                "eventNumber": 2,
                "eventStatus": "UPCOMING",
                "eventLocation": "Red Bull Ring, Austria",
                "eventLocationGroup": "Red Bull Ring, Austria"
              }
            ]

Fetch Formula 1 Event Winner Odds

View API

                    
            {
              "eventId": "f1:2127ea10-6110-4ffd-9403-3e33fc0929de",
              "oddType": "eventWinner",
              "eventWinner": [
                {
                  "id": "636d414b-8d24-49d2-a9d8-57ec650a4e0e",
                  "position": 1,
                  "probability": 0.8,
                  "odds": 1.344,
                  "athlete": {
                    "id": "636d414b-8d24-49d2-a9d8-57ec650a4e0e",
                    "firstName": "Max",
                    "middleName": "",
                    "lastName": "Verstappen",
                    "nationality": "NL",
                    "stance": ""
                  }
                }
              ]
            }

Formula Drift link

Formula 1 is the pinnacle of motorsport, featuring the fastest cars, skilled drivers, and cutting-edge technology in a global championship known for its high-speed races and intense competition.

World Champions are determined by the highest total rankings points for the season.

Leagues, Tours and Series link

League	Tour	Season	Contests	Markets per Contest	Offer Status
Group E	Jul - Mar	10	148 - 306	Offered

Contest Formats link

Markets and Wagering Times link

Event Trading Lifecycle:

Upload Schedule
Event status moves to “Upcoming” or “Next” (pre-match)
1. Alt Sports Data receives participant list via official API, and trader uploads Base Projections for each participating athlete. Participants list can be overwritten by the API when changes are made before the contest.
2. Trader maintains Event Seeds list against any athlete withdrawals or replacements until event status becomes “In-Window” and then subsequently, “Live”
3. Wagering may open for Futures
Event Status moves to “In-Window”
1. Competition can now become “Live” at the scheduled time
2. API data triggers event Live status, which is confirmed by the trader
3. Wagering may open for Solo Qualifying Lap, and all other events following confirmation of seed list for Battle bracket, including Battle bracket matchups
Event Status moves to “Live”
1. The trader confirms the start time in the trader interface, which is triggered by official API data.
2. Wagering on the first iteration of Futures closes.
3. Wagering on Solo Qualifying Lap closes.
Solo Qualifying Lap ends
1. The API delivers final lap times to Alt Sports Data, and the trader confirms any penalties applied, along with the final results
2. The trader settles bets as appropriate
3. The Battle bracket is now seeded and odds are generated
4. Wagering is open for Battle bracket
Battle Bracket battle 1 starts
1. API data triggers the start of the first Battle in the Battle bracket
2. Wagering for Battle bracket Battle 1 closes, while all other battles in the first battle round remain open
3. API delivers results and end-time, trader confirms and settles or voids bets as appropriate
Battle Brackets battle 2 starts
1. From here forward, the same open and close of wagering applies to battles, heats or races that start via API trigger
2. All results are confirmed by a trader before being settled or voided as appropriate

Markets

We offer standard markets for Futures, with realtime updates as a contest progresses. We also offer multiple markets and props.

Example Futures:

Athlete A wins contest overall (first place overall)
Athlete podiums (finishes first, second or third place overall)
Fastest Joker Lap Time overall
Fastest race time overall over/under

Example Matchups:

Athlete A places better in the event overall than Athlete B
Athlete C has a better Round Score than Athlete D

Example Props:

Athlete E makes more than 2 trick attempts in the Qualifying Round
Athlete F loses Battle with a faster Joker Lap than opponent
Total board changes in Opening Round over/under

API Integration

All of our API endpoints can be accessed via an HTTP request using your API key. The API key can be passed using the following HTTP request header.
X-API-KEY: {key}

The API for each sport has been separated by adding a sport identifier to the API path. For instance, all Nitro Rallycross APIs reside under /api/v1/nrx/*.

Here is a link to detailed documentation and a link to try it for yourself.

Schema Details and Response Samples

Fetch Formula Drift Events

View API

                    
            [
              {
                "id": "fdrift:2127ea10-6110-4ffd-9403-3e33fc0929de",
                "name": "Formula Drift - St. Louis",
                "tourName": "Formula Drift",
                "startDate": "2023-07-13T10:00:00Z",
                "endDate": "2023-07-15T12:00:00Z",
                "year": 2023,
                "eventNumber": 2,
                "eventStatus": "UPCOMING",
                "eventLocation": "St. Louis, Missouri, USA",
                "eventLocationGroup": "St. Louis, Missouri, USA"
              }
            ]

Fetch Formula Drift Event Winner Odds

View API

                    
            {
              "eventId": "fdrift:2127ea10-6110-4ffd-9403-3e33fc0929de",
              "oddType": "eventWinner",
              "eventWinner": [
                {
                  "id": "636d414b-8d24-49d2-a9d8-57ec650a4e0e",
                  "position": 1,
                  "probability": 0.8,
                  "odds": 1.344,
                  "athlete": {
                    "id": "636d414b-8d24-49d2-a9d8-57ec650a4e0e",
                    "firstName": "Simen",
                    "middleName": "",
                    "lastName": "Olsen",
                    "nationality": "NO",
                    "stance": ""
                  }
                }
              ]
            }

MotoGP link

Formula 1 is the pinnacle of motorsport, featuring the fastest cars, skilled drivers, and cutting-edge technology in a global championship known for its high-speed races and intense competition.

World Champions are determined by the highest total rankings points for the season.

Leagues, Tours and Series link

League	Tour	Season	Contests	Markets per Contest	Offer Status
Group E	Jul - Mar	10	148 - 306	Offered

Contest Formats link

Markets and Wagering Times link

Event Trading Lifecycle:

Upload Schedule
Event status moves to “Upcoming” or “Next” (pre-match)
1. Alt Sports Data receives participant list via official API, and trader uploads Base Projections for each participating athlete. Participants list can be overwritten by the API when changes are made before the contest.
2. Trader maintains Event Seeds list against any athlete withdrawals or replacements until event status becomes “In-Window” and then subsequently, “Live”
3. Wagering may open for Futures
Event Status moves to “In-Window”
1. Competition can now become “Live” at the scheduled time
2. API data triggers event Live status, which is confirmed by the trader
3. Wagering may open for Solo Qualifying Lap, and all other events following confirmation of seed list for Battle bracket, including Battle bracket matchups
Event Status moves to “Live”
1. The trader confirms the start time in the trader interface, which is triggered by official API data.
2. Wagering on the first iteration of Futures closes.
3. Wagering on Solo Qualifying Lap closes.
Solo Qualifying Lap ends
1. The API delivers final lap times to Alt Sports Data, and the trader confirms any penalties applied, along with the final results
2. The trader settles bets as appropriate
3. The Battle bracket is now seeded and odds are generated
4. Wagering is open for Battle bracket
Battle Bracket battle 1 starts
1. API data triggers the start of the first Battle in the Battle bracket
2. Wagering for Battle bracket Battle 1 closes, while all other battles in the first battle round remain open
3. API delivers results and end-time, trader confirms and settles or voids bets as appropriate
Battle Brackets battle 2 starts
1. From here forward, the same open and close of wagering applies to battles, heats or races that start via API trigger
2. All results are confirmed by a trader before being settled or voided as appropriate

Markets

We offer standard markets for Futures, with realtime updates as a contest progresses. We also offer multiple markets and props.

Example Futures:

Athlete A wins contest overall (first place overall)
Athlete podiums (finishes first, second or third place overall)
Fastest Joker Lap Time overall
Fastest race time overall over/under

Example Matchups:

Athlete A places better in the event overall than Athlete B
Athlete C has a better Round Score than Athlete D

Example Props:

Athlete E makes more than 2 trick attempts in the Qualifying Round
Athlete F loses Battle with a faster Joker Lap than opponent
Total board changes in Opening Round over/under

API Integration

All of our API endpoints can be accessed via an HTTP request using your API key. The API key can be passed using the following HTTP request header.
X-API-KEY: {key}

The API for each sport has been separated by adding a sport identifier to the API path. For instance, all Nitro Rallycross APIs reside under /api/v1/nrx/*.

Here is a link to detailed documentation and a link to try it for yourself.

Schema Details and Response Samples

Fetch MotoGP Events

View API

                    
            [
              {
                "id": "motogp:2127ea10-6110-4ffd-9403-3e33fc0929de",
                "name": "Formula Drift - St. Louis",
                "tourName": "Formula Drift",
                "startDate": "2023-07-13T10:00:00Z",
                "endDate": "2023-07-15T12:00:00Z",
                "year": 2023,
                "eventNumber": 2,
                "eventStatus": "UPCOMING",
                "eventLocation": "St. Louis, Missouri, USA",
                "eventLocationGroup": "St. Louis, Missouri, USA"
              }
            ]

Fetch MotoGP Event Winner Odds

View API

                    
            {
              "eventId": "motogp:2127ea10-6110-4ffd-9403-3e33fc0929de",
              "oddType": "eventWinner",
              "eventWinner": [
                {
                  "id": "636d414b-8d24-49d2-a9d8-57ec650a4e0e",
                  "position": 1,
                  "probability": 0.8,
                  "odds": 1.344,
                  "athlete": {
                    "id": "636d414b-8d24-49d2-a9d8-57ec650a4e0e",
                    "firstName": "Simen",
                    "middleName": "",
                    "lastName": "Olsen",
                    "nationality": "NO",
                    "stance": ""
                  }
                }
              ]
            }

Motocross link

Formula 1 is the pinnacle of motorsport, featuring the fastest cars, skilled drivers, and cutting-edge technology in a global championship known for its high-speed races and intense competition.

World Champions are determined by the highest total rankings points for the season.

Leagues, Tours and Series link

League	Tour	Season	Contests	Markets per Contest	Offer Status
Group E	Jul - Mar	10	148 - 306	Offered

Contest Formats link

Markets and Wagering Times link

Event Trading Lifecycle:

Upload Schedule
Event status moves to “Upcoming” or “Next” (pre-match)
1. Alt Sports Data receives participant list via official API, and trader uploads Base Projections for each participating athlete. Participants list can be overwritten by the API when changes are made before the contest.
2. Trader maintains Event Seeds list against any athlete withdrawals or replacements until event status becomes “In-Window” and then subsequently, “Live”
3. Wagering may open for Futures
Event Status moves to “In-Window”
1. Competition can now become “Live” at the scheduled time
2. API data triggers event Live status, which is confirmed by the trader
3. Wagering may open for Solo Qualifying Lap, and all other events following confirmation of seed list for Battle bracket, including Battle bracket matchups
Event Status moves to “Live”
1. The trader confirms the start time in the trader interface, which is triggered by official API data.
2. Wagering on the first iteration of Futures closes.
3. Wagering on Solo Qualifying Lap closes.
Solo Qualifying Lap ends
1. The API delivers final lap times to Alt Sports Data, and the trader confirms any penalties applied, along with the final results
2. The trader settles bets as appropriate
3. The Battle bracket is now seeded and odds are generated
4. Wagering is open for Battle bracket
Battle Bracket battle 1 starts
1. API data triggers the start of the first Battle in the Battle bracket
2. Wagering for Battle bracket Battle 1 closes, while all other battles in the first battle round remain open
3. API delivers results and end-time, trader confirms and settles or voids bets as appropriate
Battle Brackets battle 2 starts
1. From here forward, the same open and close of wagering applies to battles, heats or races that start via API trigger
2. All results are confirmed by a trader before being settled or voided as appropriate

Markets

We offer standard markets for Futures, with realtime updates as a contest progresses. We also offer multiple markets and props.

Example Futures:

Athlete A wins contest overall (first place overall)
Athlete podiums (finishes first, second or third place overall)
Fastest Joker Lap Time overall
Fastest race time overall over/under

Example Matchups:

Athlete A places better in the event overall than Athlete B
Athlete C has a better Round Score than Athlete D

Example Props:

Athlete E makes more than 2 trick attempts in the Qualifying Round
Athlete F loses Battle with a faster Joker Lap than opponent
Total board changes in Opening Round over/under

API Integration

All of our API endpoints can be accessed via an HTTP request using your API key. The API key can be passed using the following HTTP request header.
X-API-KEY: {key}

The API for each sport has been separated by adding a sport identifier to the API path. For instance, all Nitro Rallycross APIs reside under /api/v1/nrx/*.

Here is a link to detailed documentation and a link to try it for yourself.

Schema Details and Response Samples

Fetch Motocross Events

View API

                    
            [
              {
                "id": "motocrs:2127ea10-6110-4ffd-9403-3e33fc0929de",
                "name": "RedBud National",
                "tourName": "Pro Motocross",
                "startDate": "2023-07-01T10:00:00Z",
                "endDate": "2023-07-02T12:00:00Z",
                "year": 2023,
                "eventNumber": 2,
                "eventStatus": "UPCOMING",
                "eventLocation": "Buchanan, MI",
                "eventLocationGroup": "Buchanan, MI"
              }
            ]

Fetch Motocross Event Winner Odds

View API

                    
            {
              "eventId": "motocrs:2127ea10-6110-4ffd-9403-3e33fc0929de",
              "oddType": "eventWinner",
              "eventWinner": [
                {
                  "id": "636d414b-8d24-49d2-a9d8-57ec650a4e0e",
                  "position": 1,
                  "probability": 0.8,
                  "odds": 1.344,
                  "athlete": {
                    "id": "636d414b-8d24-49d2-a9d8-57ec650a4e0e",
                    "firstName": "Jett",
                    "middleName": "",
                    "lastName": "Lawrence",
                    "nationality": "AUS",
                    "stance": ""
                  }
                }
              ]
            }