Updates

2025

15th February

Schema changes

1. Breaking change against onPoolDividendChanged changes from value to decimalAmount and currency to currency object, see below for changes.

   subscription {
    onPoolDividendChanged {
        dividends {
            dividend {
                amounts {
                    value       // no longer supported
                    currency    // no longer supported
                }
                amounts {
                    decimalAmount
                    currency {
                        code
                    }
                }
            }
        }
    }
   }
   

2. Deprecation of GrossAmount and NetAmount in PoolTotalChanged Subscription. These fields will be replaced by GrossAmounts and NetAmounts, which are collections of Money objects providing detailed total breakdowns.
3. Affected Properties
   • Total
   • Guarantee
   • CarryIn
   • Funds - Total
   • Funds - CarryIn
4. Example

   subscription {
    onPoolTotalChanged {
        total {
            grossAmount { value currency } // will be removed in future versions
            netAmount { value currency }   // will be removed in future versions
            grossAmounts {
                decimalAmount
                currency {
                    code
                }
            }
            netAmounts {
                decimalAmount
                currency {
                    code
                }
            }
        }
        guarantee {
            grossAmount { value currency } // will be removed in future versions
            netAmount { value currency }   // will be removed in future versions
            grossAmounts {
                decimalAmount
                currency {
                    code
                }
            }
            netAmounts {
                decimalAmount
                currency {
                    code
                }
            }
        }
        carryIn {
            grossAmount { value currency } // will be removed in future versions
            netAmount { value currency }   // will be removed in future versions
            grossAmounts {
                decimalAmount
                currency {
                    code
                }
            }
            netAmounts {
                decimalAmount
                currency {
                    code
                }
            }
        }
        funds {
            carryIn {
                grossAmount { value currency } // will be removed in future versions
                netAmount { value currency }   // will be removed in future versions
                grossAmounts {
                    decimalAmount
                    currency {
                        code
                    }
                }
                netAmounts {
                    decimalAmount
                    currency {
                        code
                    }
                }
            }
            total {
                grossAmount { value currency } // will be removed in future versions
                netAmount { value currency }   // will be removed in future versions
                grossAmounts {
                    decimalAmount
                    currency {
                        code
                    }
                }
                netAmounts {
                    decimalAmount
                    currency {
                        code
                    }
                }
            }
        }
    }
   }
   

10th February

Schema changes

1. Replace fragment spread on product with Type:
2. Instead of querying and spreading fragments directly on product, the schema will now use type.
3. Example:

    products {
      nodes {
        id
        name
        type {
          ... on BettingProduct { // apply fragment on type instead of product
            legs {
            nodes {
              id
              selections {
                nodes {
                  id
                  name
                  bettingSelectionId
                }
              }
            }
          }
        }
        ... on BettingProduct { // will be removed in future versions
          legs {
            nodes {
              id
              selections {
                nodes {
                  id
                  name
                  bettingSelectionId
              }
            }
          }
        }
      }
    }
   }
   

4. Replace EventId with Event:
5. Instead of querying the eventId directly, the schema will use event to provide a richer representation
6. Example:

   eventId // will be removed in future versions
   event {
       id
       name
       venue {
           name
       }
   }
   

7. Replace EventCompetitorId with Competitor:
8. The field eventCompetitorId will be replaced with competitor to encapsulate competitor details directly and provide a structured representation.
9. Example:

   eventCompetitorId // will be removed in future versions
   competitor {
      id
      name
      entryStatus
      details {
          ... on HorseDetails {
              clothNumber
          }
          ... on GreyhoundDetails {
              trapNumber
          }
      }
   }
   

10. Replace EventCompetitor with Competitor
11. Any references to eventCompetitor will now use competitor, aligning with the updated naming convention.

12. Move type-specific fields from fragment spreads to details

13. Instead of using inline fragments on eventCompetitor, type-specific fields (e.g., trapNumber or clothNumber) will now reside under a details field within competitor.

14. Example:

// Old:
eventCompetitor { // will be removed in future versions
    ... on GreyhoundEventCompetitor {
        trapNumber
    }
    ... on HorseRacingEventCompetitor {
        clothNumber
    }
}

// New:
competitor {
    details {
        ... on GreyhoundDetails {
            trapNumber
        }
        ... on HorseDetails {
            clothNumber
        }
    }
}

1. The competitors field is being deprecated in favour of eventCompetitors

2. Example:

  events {
      nodes {
          competitors { // will be removed in future versions
              nodes {
                  id
                  name
                  entryStatus
                  ... on HorseRacingEventCompetitor {
                      clothNumber
                  }
                  ... on GreyhoundEventCompetitor {
                      trapNumber
                  }
              }
          }
          eventCompetitors {
              nodes {
                  id
                  name
                  entryStatus
                  details {
                      ... on HorseDetails {
                          clothNumber
                      }
                      ... on GreyhoundDetails {
                          trapNumber
                      }
                  }
              }
          }
      }
  }

20th January

• Adding bet type examples
• Adding Trio and Show

2024

1st February

• New features
• Customer query to retrieve a balances in the account.

2023

20th December

• New features
• Web socket available for bet and product changes.

17th November

• Adding bet types
• Adding placepot7, superfecta and irish jackpot.

2nd November

• Schema changes
• Products query date search parameter renamed from sinceDate to date.
• date will be defaulted to current day if not set and no other search filters set.
• Multiple queries will be required to cover a date range of more than one day and combined by the API consumer.

10th October

• New Fixes
• Performance improvements

13th September

• New Features
• Lines on product which contains the live odds for the win and place pools.
• Pool on the product contains the live pool total and all the pool data.
• Bet Rules are on the product.
• All odds changes available through a file download.
• Link through from bets to product and event details.
• Link through from product to event details.

1st August

• New Features
• BettingProducts now include pricing information if available
• Change
• Event ID are now descriptive names

25th July

• New Features
• Retrieve a list of bets/tickets by product type

10th July

• New Features
• Bets are now validated with improved error messages returned

27th June

• New Features
• Retrieve a list of bets by date
• Bet placement now performs faster

9th June

• New Features
• Retrieve a list of available events
• Products.Legs now contain the Event information
• Fixes
• DateTime now includes Zulu offset

29th May April

• New Features
• Pagination now available on products, bets and events
• Change
• Products ID are now GUIDs

12th May April

• New Features
• Updated Schema for Product/Bet to cater for future additions
• Bets and tickets now contain a supplied client bet id and tote generated bet id
• New Authentication methods - API Key

1st May April

• New Features
• Improved bet settlement where race information is initially unavailable
• Fixes
• Idempotency checks to prevent duplicate bet placement

3rd April

• New Features
• Retrieve a list of bets that have been placed
• Retrieve a list of tickets, include a list of bets on that tickets

20th March

• New Features
• Partner API released
• Retrieve a list of available product
• Place bets
  • Partner API released
  • Retrieve a list of available product
  • Place bets