sportradar.comSportradar Support Portal

Environments

Betradar offers the Unified odds Feed in three different environments to our clients to ensure better stability, reliability, and user experience. These environments have a distinguished purpose and properties.

Integration Environment

The Integration environment is the entry point for working with the Unified Odds Feed. It delivers live updates that closely resemble those in the production environment. However, it operates on a 24/5 schedule, available 24 hours a day from Monday to Friday. Access is not available on weekends, as connections are terminated and new sessions cannot be established during that time

Note

While the testing environments may experience occasional instability, they are designed to support development and integration. Once clients gain access to the production environment, they can expect maximum stability, along with high reliability and an optimal user experience.

The integration environment is available for development, qualitative analysis, and testing purposes. Live Odds are slightly delayed in this environment (about 1 minute). This environment includes the latest features and additions before they become available in the production environment.

During the weekend there will be some planned 2-hour disconnections at fixed times:

Saturday: 14:00 - 16:00 UTC and 20:00 - 22:00 UTC

Sunday: 00:00 - 02:00 UTC and 13:00 - 15:00 UTC

Note

We recommend performing recoveries only when you are receiving alive messages. Recoveries sent during the planned downtime are executed (although they are not read by you on the client-side), which means you risk running into the rate limit when the service is running.

The integration environment uses the following components:

To generate access tokens in the integration environment, navigate to Integration Portal

Replay Environment

Betradar provides a Replay Server designed for testing and reproducing historical events. It allows clients to reprocess past events by resending all associated messages exactly as they were originally delivered. This server operates as a dedicated message queue, controlled primarily via a separate RESTful API (although SDK methods are also available through the ReplayManager interface). We recommend using the REST API through the iodocs platform for ease of use and improved reliability.

How it works

Clients begin by defining the specific match (or lists of matches) they want to replay. Once the replay is started, the server sends all relevant messages for those matches to a dedicated replay user that's independent of the client’s own CTRL configuration and templates.

This means:

  • Client Templates (e.g. CTRL odds settings) are not considered.

  • Events from sports you don’t normally have access to can still be replayed.

  • Replayed messages remain consistent regardless of client-side configuration.

  • If the match was recorded with the special user, you can replay it as long as it's older than 48 hours.

  • Events remain replayable indefinitely, although Betradar reserves the right to remove events older than 2 years.

Supported Controls and Parameters

Clients can tailor their replay using the following options:

  • Build a playlist: Include individual matches, stages, seasons, or entire tournaments.

  • Replay speed: Run events faster than real-time (by default: 10x).

  • Maximum delay between messages: Useful for controlling long pre-match delays.

  • Parallel playback: Run multiple matches simultaneously.

  • Timestamp rewrite: Replace original timestamps with current time, simulating a real-time experience.

  • Node ID filtering: To Distinguish between playlists on different nodes.

  • Scenario-based playback: Use predefined sets of 100–200 or 450 events for stress testing and edge cases.

Note

The replay environment can be accessed 24/7/365 using either integration or production token.

Production Environment

When the client integration is nearly ready for Production, it is time to promote the client to the production environment, which is available 24/7/365. Before this can be done, we will do a technical review from our end to make sure your usage of the Unified Odds Feed is ready for production from our point of view.

The production environment provides real-time messaging and up-to-date information about various ongoing sports events.

The production environment uses the following components:

To generate access tokens in a production environment, navigate to Production Portal interface.

For detailed information, refer to UOF - Generating Access Tokens

Note

Please note that the production environment requires a production token, which is different than the one used for integration. * Production access is only provided after the integration is completed.

Our endpoints are backed by Content Delivery Network (CDN) solution to ensure low latency from geographically distributed locations. The DNS names (mq.betradar.com and api.betradar.com) will point to a set of IP addresses, and those IP addresses can change from time to time without prior notice.

If you currently whitelist our IP for outgoing traffic, we can not supply you with a fixed set of IPs for this, as they can change from time to time and without prior notice.

PreviousAccess MethodsNextLanguage Support

Last updated

Was this helpful?