Third Party Odds

This page will help you get started with Sportradar's Third-Party Odds Platform. You'll be up and running in a jiffy!

Overview

The Third-Party Odds Platform provides your REST APIs that will enable you to seamlessly integrate with Sportradar and distribute specialised odds for your markets to bookmakers through Unified Odds Feed.

Assumptions & Requirements

1. Data schema - Compliance to S3P (Sportradar Standard Sports Protocol) specification is mandated. S3P defines a standard for communication between components used to acquire, process and distribute sports data in Sportradar

2. Markets - Markets are created by Sportradar and unique IDs generated. You need to map your markets with these specific IDs. Similarly fixture and player IDs.

3. Heartbeat - A Heartbeat message must be sent once every 5 seconds per match, if there is no odds message during that time interval. If there is at least 1 odds message in 5 sec window, then heartbeat message is not required. If the Heartbeat or Odds change message was not received, the market line will be automatically deactivated, and if you are subscribed to market_deactivation notifications, you will receive information about it.

4. Message Collation - We expect maximum 1 message per sec per match from you. If your system is able to generate more than 1 odds update within 1 sec, then you need to collate those updates and send as 1 single message each sec.

Continue Reading:

For full details, including examples and advanced usage, refer to the third-party documentation

Visit Third-Party Docs