> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/uof/bet-builder/intro.md).

# Intro

Bet Builder is a service that **enables you to build your own** **Bet Builder feature**, giving punters the freedom to create **highly personalized betting experiences**. By combining multiple selections, whether within a single match or across different matches, you can offer engaging, flexible betting options that drive both **margin growth** and **player satisfaction**.

Check our [product sheet ](https://resources.sportradar.com/custom-bet/bet-builder-lf)to understand Bet Builder on one page.

**Key Benefits / Use Cases**

* You can customize your odds pricing for the Bet Builder by choosing a specific odds key or using any odds source to define the margin.
* You can enhance your punters' engagement by using our AI-driven pre-built recommendations, or our highly customizable combination options.
* You can choose the best integration solution for your business:
  * **API solution** (supports [SDK](https://docs.betradar.com/display/BD/UOF+-+SDK)) to design your own front end and tailor the experience fully.
  * **Front-end widget solution** for faster integration into your existing platform. - *Reach out to our sales or support team for more information.*

#### **2. Supported Sports & Markets** <a href="#id-wip-custombetapidocumentationredesign-2.supportedsports-and-markets" id="id-wip-custombetapidocumentationredesign-2.supportedsports-and-markets"></a>

Bet Builder uses a limited number of selected markets provided in our *Unified odds feed* product for each supported sport.

Check out the [Bet Builder Market List page](https://docs.sportradar.com/uof/introduction/market-overview-uof-and-cb) for the detailed list of markets we support.&#x20;

{% hint style="info" %}
**Note:**

* For all Total and Handicap lines, we only support x.5 market lines.
* All Asian outcomes are not supported in Bet Builder, as we do not currently provide calculations for partly-voided outcomes.&#x20;
  {% endhint %}

| Sport             | Pre-match               | Live                    | Tournament                                                                                              |
| ----------------- | ----------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------- |
| Soccer            | ✅                       | ✅                       | Bet Builder supports all tournaments for which the specific market is supported in the UOF feed.        |
| Basketball        | ✅                       | ✅                       | Bet Builder supports all tournaments for which the specific market is supported in the UOF feed.        |
| Tennis            | ✅                       | ✅                       | Bet Builder supports all tournaments for which the specific market is supported in the UOF feed.        |
| Ice Hockey        | ✅                       | ✅                       | Bet Builder supports all tournaments for which the specific market is supported in the UOF feed.        |
| American Football | ✅                       | :white\_check\_mark:    | Bet Builder supports NFL now. Other tournaments coming soon.                                            |
| Baseball          | ✅                       | :white\_check\_mark:    | Bet Builder supports all tournaments for which the specific market is supported in the UOF feed.        |
| Cricket           | ✅                       | :white\_check\_mark:    | Bet Builder supports all tournaments except Test matches.                                               |
| Volleyball        | ✅                       | Coming in November 2026 | Bet Builder supports all tournaments for which the specific market is supported in the UOF feed.        |
| MMA               | :white\_check\_mark:    |                         | Bet Builder supports all tournaments for which the specific market is supported in the UOF feed.        |
| Rugby             | :white\_check\_mark:    | Coming in November 2026 | Bet Builder supports all Rugby Union events for which the specific market is supported in the UOF feed. |
| Dart              | Coming in November 2026 | To be planned           | Bet Builder supports all tournaments for which the specific market is supported in the UOF feed.        |

#### **3. Our Solutions** <a href="#id-wip-custombetapidocumentationredesign-3.oursolutions" id="id-wip-custombetapidocumentationredesign-3.oursolutions"></a>

These are the 2 solution you can choose to build your own Bet Builder feature.

<table data-full-width="false"><thead><tr><th>Solution</th><th>When to choose it?</th></tr></thead><tbody><tr><td>API</td><td><ul><li>Use this if you want a fully customized front-end experience.</li><li>Provides maximum flexibility to design your own interface and user experience.</li><li>Supports <a href="https://docs.betradar.com/display/BD/UOF+-+SDK">SDK</a></li></ul></td></tr><tr><td>Front-end</td><td><ul><li>Use this if you want fast, easy integration. </li><li>The widget can be iframed into your website for quick deployment. Ideal if you have limited time or resources and want to test the feature quickly. You can opt for our API solution afterwards when you finish building your own front end.</li><li>Demo: <a href="https://widgets.sir.sportradar.com/custom-bet#matches:(matchId:50852263,sportId:1)">https://widgets.sir.sportradar.com/custom-bet#matches:(matchId:50852263,sportId:1)</a></li><li>Reach out to our sales or support team for more information.</li></ul></td></tr></tbody></table>

**API solution**

These are the 4 main API endpoints you can use to build your Bet Builder. Check each page for the detailed guide to each API endpoint.

* [**Available Selection**](https://docs.sportradar.com/uof/bet-builder/api/available-selections.md): Gives you all available markets that can be combined with the Bet Builder.
* [**Calculate**](https://docs.sportradar.com/uof/bet-builder/api/calculate.md)**:** Returns the odds and probability of the selected combination. Also provides remaining available selections.
* [**Calculate Filter**](https://docs.sportradar.com/uof/bet-builder/api/calculate-filter.md)**:** Returns the same information as Calculate (odds and probabilities). Additionally, flags selections that conflict with the current combo.
* [**Pre-Built**](https://docs.sportradar.com/uof/bet-builder/api/pre-built-bet-recommendation.md)**:** Provides AI-powered personalized recommended pre-built combos with odds pricing.
* [Voided Recalculation](https://docs.sportradar.com/uof/bet-builder/api/void-recalculation.md): Gives you precomputed odds for all possible single-void scenarios.

**Other Features we support**

* **Source-Agnostic solution:** you can **use any odds sources** you want, and we will harmonize your single odds with the Bet Builder odds to generate the most competitive pricing. [Check here for the guide](https://docs.sportradar.com/uof/bet-builder/source-agnostic-solution-harmonization-feature.md).
* **Multi-match request:** Combine up to 20 matches with a maximum of 10 selections per match. [Check here for the guide. ](https://docs.sportradar.com/uof/bet-builder/api/calculate.md)
* **Multi-sport request:** Combine up to 20 matches across multiple sports with a maximum of 10 selections per match. [Check here for the guide.](https://docs.sportradar.com/uof/bet-builder/api/calculate.md)
* **Combination flexibility:** You can freely combine any markets as long as they do not conflict. Even if two selections imply the same outcome, we still allow the combination—helping you increase bet volume and reduce ticket rejection rates.

| Sports            | Source-Agnostic      | Multi-match & Multi-sport |
| ----------------- | -------------------- | ------------------------- |
| Soccer            | ✅                    | ✅                         |
| Basketball        | ✅                    | ✅                         |
| Tennis            | :white\_check\_mark: | :white\_check\_mark:      |
| Ice Hockey        | ✅                    | ✅                         |
| American Football | ✅                    | ✅                         |
| Baseball          | ✅                    | ✅                         |
| Cricket           | ✅                    | ✅                         |
| Volleyball        | ✅                    | ✅                         |
| MMA               | :white\_check\_mark: | :white\_check\_mark:      |

#### **4.** Combination Rules <a href="#id-wip-custombetapidocumentationredesign-4.combinationrules" id="id-wip-custombetapidocumentationredesign-4.combinationrules"></a>

* Max 10 selections per match and Max 20 matches in one request. Matches can belong to the same sport or different sports.&#x20;
* All combinations are allowed as long as they do not conflict, meaning thst the selections cannot happen at the same time. &#x20;
* If you are not using [harmonization](https://docs.sportradar.com/uof/custombet-cb/source-agnostic-solution-harmonization-feature) (not sending us your single odds), then you will not be able to combine selections that imply same result. You will receive an error message “One or more market selections imply a similar outcome to another market selection.”&#x20;

#### **5. Environments** <a href="#id-wip-custombetapidocumentationredesign-5.environments" id="id-wip-custombetapidocumentationredesign-5.environments"></a>

<table data-full-width="false"><thead><tr><th>Environments</th><th>Guideline</th></tr></thead><tbody><tr><td>Integration</td><td><p>Use this environment for <strong>testing and development</strong> before release.</p><p><em>Note:</em> Since it is also used for ongoing development, testing, and deployments, results may differ from production. Performance and reliability are not guaranteed.</p></td></tr><tr><td>Production</td><td><p>Use this environment for <strong>real user traffic and live experiences</strong>.</p><p><em>Note:</em> Do not use for testing to ensure production requests are processed reliably.</p></td></tr></tbody></table>

For more information about API availability, access restrictions and functionality related to these, please see the [Unified Odds feed integration documentation.](https://docs.betradar.com/pages/viewpage.action?pageId=2162692)&#x20;

#### **6. API Access & Data Availability** <a href="#id-wip-custombetapidocumentationredesign-6.apiaccess-and-dataavailability" id="id-wip-custombetapidocumentationredesign-6.apiaccess-and-dataavailability"></a>

**Products Access**

Bet Builder is available through separate Pre-Match and Live packages. For example, if you subscribe to the Pre-Match Bet Builder package, you can access all sports that support Pre-Match Bet Builder across all endpoints. The same applies to the Live package. Please contact your commercial representative for more information about the packages and to determine which one you need to activate.

**Rate Limit**

⚠️ Bet Builder default rate limit is 100 req/sec across all endpoints. If you need more, please reach out to your commercial representative for increase.

> ⚠️ For higher limits, please contact your commercial representative to upgrade the product.

**Data Availability**

<table data-full-width="false"><thead><tr><th>Event Type</th><th>Availablity</th></tr></thead><tbody><tr><td>Pre-match</td><td>Pre-match Bet Builder is available once you receive <em>side markets</em> (markets other than 2-way, 3-way, or totals) from UOF, until handover to Live.</td></tr><tr><td>Live</td><td><p>Live Bet Builder is available after handover from Pre-match to Live odds, until the match ends.</p><p>And you need to book the Live event on our Live Booking Calendar.</p></td></tr><tr><td>Completed matches</td><td>Not supported</td></tr></tbody></table>

⚠️ Betpal (Producer 4) is supported on Bet Builder. However, it is strongly recommended to enable the Harmonization feature. Without Harmonization, customers are advised that Bet Builder will use underlying probabilities to form Bet Builder odds and not ALPHA odds probabilities. We recommend all customers to use Harmonization to have the most optimum Bet Builder Odds available.

#### **7. Odds & Margins** <a href="#id-wip-custombetapidocumentationredesign-7.odds-and-margins" id="id-wip-custombetapidocumentationredesign-7.odds-and-margins"></a>

**How Odds Are Calculated:**

<figure><img src="https://1868790214-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1KlIQPveu0EGYCTI8DL1%2Fuploads%2Fdl4rkomGKixD7sRsd5Py%2FSlide5.jpg?alt=media&amp;token=06842d7a-ff76-43d6-a976-0acbd498bb16" alt=""><figcaption></figcaption></figure>

We use your single-selection odds to calculate Bet Builder odds. This ensures that the resulting odds are aligned with your single odds and provides consistent, competitive pricing.

1. **How it works**

When you combine selections from different markets (e.g., Market A and Market B), our model calculates the correlation factor between them and applies it to the combined single odds.

Calculation formula:

Bet Builder odds = Single odds (Market A) × Single odds (Market B) × Correlation factor

Simply include the odds for each individual selection in your request. For example:

```
<selection id=“sr:match:14736961” market_id=“14" specifiers=“hcp=1:0” outcome_id=“1711" odds=“2.4”/> <selection id=“sr:match:14736961" market_id=“26” outcome_id=“70" odds=“3.5”/>
```

2. **Additional functionality**

This approach is source-agnostic, meaning you can use odds from any source you choose. For more details, see our Source-Agnostic Solution and Harmonization Feature. Managing your odds limits: You can configure a maximum cap for harmonized odds to keep the resulting odds within your risk management limits. Please contact our support team to have this limit configured.

\
**Odds Key Ladder Mapping**

{% hint style="warning" %}
⚠️ If you are still using the Ladder for Bet Builder, please move to the Margin approach mentioned above, which will give you better odds quality and combination flexibility. This is just a reference for clients that are not yet moved the the latest margin setting approach.
{% endhint %}

| fair odds | Aggressive (105) | Moderate (110) | moderate (flat) | Conservative (115) |
| --------- | ---------------- | -------------- | --------------- | ------------------ |
| 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                |

***

#### **8. Best Practices** <a href="#id-wip-custombetapidocumentationredesign-8.bestpractices" id="id-wip-custombetapidocumentationredesign-8.bestpractices"></a>

* **Punter Placing a Bet**

  * Use **Available Selection endpoint** to show users all possible markets.
  * When a user selects a combo, call **Calculate Filter endpoint** to get odds and disable conflicting selections.
  * Before placing a bet, call **Calculate endpoint** for a fast, accurate odds response.
  * When the punter places the bet, call the **Void Recalculation endpoint** using the same selections to get the precomputed void combination odds. If one selection is later declared void, use the returned odds to settle/update the remaining valid selections. &#x20;

  **Offering Pre-Built Recommendation**

  * Get recommended pre-built combos and display it on the event page or homepage for quick bet placement.
  * For Pre-match Pre-Built recommendations, we recommend caching the odds price for 15 seconds, since Pre-match prices rarely change quickly, which reduces excessive API calls.
  * If you need to update the odds for a specific pre-built, call **Calculate endpoint** endpoint for a fast response without the need for filtering.

  **Handling Settlements & Voided Markets:**

  * Store the final accepted Bet Builder ticket
  * Listen to the feed for settlements of individual markets.
    * Won: all selections are won
    * Lost: at least one selection is lost
    * If one leg is voided, update the price for the remaining selections. You can do this with our Void Recalculation endpoint.
  * The settlement logic should follow the same principles as handling combination bets across different events.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sportradar.com/uof/bet-builder/intro.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
