Availability and Environments
This section explains the availability and environments for using the CustomBet API. It outlines where and how to test your integration safely, what to expect from each environment, and when the API is available for both pre-match and live events.
Environments
CustomBet has a production and integrations environment just like the Unified Odds feed, but no replay server.
Please don't use production for testing, use the integration environment for testing requirements.
Integration Environment Guidelines: It is a shared, non-production space designed for testing and validating new features, APIs, and system interactions. Please note that this environment is inherently unstable, as ongoing development, testing, and deployments may result in temporary disruptions, bugs or performance issues. While you are welcome to use it for testing purposes at any time, we recommend doing so with the understanding that performance and reliability cannot be guaranteed.
For more information about API availability, access restrictions and functionality related to these, please see the Unified Odds feed integration documentation. CustomBet is also supported by our SDK.
Data availability
For Pre-match events, Custom Bet API will be available after you receive side markets from UOF. And it will available until the handover.
Side markets=markets that are not 2way, 3way, or total
For Live events, Custom Bet API will be available after the handover from Pre-match to Live odds. And it will available until the match ends.
Completed matches are not supported in Custom Bet.
Rate limiting
The current rate limit for using the CustomBet is set to:
Production environment: 100 requests per second
Other environments: 20 requests per second
Higher Rate limits are available depending on the package that you are on. These limits are set at:
Custom Bet Pro: 250 requests per second
Custom Bet Premium: 500 requests per second
Please speak to your commercial representatives if you wish to apply for higher rate limits.
CustomBet ladder
The CustomBet ladder will be configurable through Betradar Ctrl (feed options > Custom Bet tab), and three are currently 3 options available.
Moderate (110)
Conservative (115)
Aggressive (105)
Please find the mapping of "fair odds" <to> "CustomBet odds" for each ladder below:
1
1
1
1
1
1,001
1,0005
1
1
1
1,02
1,015
1,01
1,01
1,005
1,05
1,04
1,03
1,03
1,02
1,1
1,08
1,07
1,07
1,05
1,2
1,17
1,15
1,16
1,12
1,4
1,36
1,32
1,33
1,28
1,7
1,63
1,57
1,6
1,51
2
1,9
1,82
1,85
1,74
2,5
2,36
2,23
2,25
2,11
3,5
3,25
3
3
2,8
5
4,5
4,1
3,8
3,8
10
8,5
7,5
6
7
20
16
14
9
12
50
40
33
18
25
100
70
50
22
30
1000
300
200
50
100
10000
750
500
70
250
100000
2000
1000
80
500
Odds control via Ctrl or Betpal Customer adjusted odds for specific selections via CTRL (pre-match) or Betpal (live) will not be reflected in CustomBet as the Betradar odds suggestions (respectively the probabilities) are taken for calculation purposes.
Selection validation
There are some rules applied to selections which need to be considered.
Restriction
Details
Only legal market combinations
team to score ({!goalnr} goal) market cannot be combined with 1st or 2nd half version of the same market
any of the above cannot be combined with player goalscorer markets
Amount of selections
limited to 10 selections
Combine across up to 5 matches for Soccer
You can make combinations across up to 5 Soccer matches e.g. 2 selections per match for 5 different matches
This is currently only available via Direct API integration with the Custom Bet API.
This is currently not supported for customers using our Front-end Visualisation widget or using ORAKO.
Combine within 1 match For Basketball & Tennis
Selections for Basketball and Tennis are only allowed for the same match. No Cross-match capabilities are currently possible.
Combine only 1 sport at a time
Combinations across different sports, e.g. Tennis & Soccer are currently not supported.
Live documentation
The CustomBet endpoints along with the normal Unified Odds API can be found on our live documentation page HERE.
Settlement implementation guidelines
Store the final accepted custom bet
Listen to the feed for settlements of single markets
A single losing selection means the whole custom bet is losing
If a market within a Custom Bet bet is voided, we recommend you to void the entire Custom Bet bet.
Only in case when all the selections are winning, custom bet is winning as well
The logic should be similar to handling combination bets on different events
Last updated
Was this helpful?