> 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/custombet-cb/api/void-recalculation.md).

# Void Recalculation

The **Void Bet Recalculation API** allows operators to continue settling a Bet Builder\
ticket when one selection is declared void, instead of voiding and refunding the\
entire bet.\
When the bet is placed, this endpoint returns the original calculation together with\
precomputed odds for every possible single-leg void scenario. If one selection\
is later voided, the client simply retrieves the corresponding precomputed odds\
and uses them to settle the remaining selections.

**Benefits**

Supports single-leg void scenarios.\
• Reduces unnecessary bet refunds.\
• Improves the customer betting experience.

**Limitations**\
\
• Only one voided selection is supported.\
• Multiple voided selections are not supported.\
• If the Bet Builder contains only 2 selections, no precomputed void\
combinations are returned. If one selection becomes void, simply use the\
original odds of the remaining selection.

\
**Integrations steps**<br>

1. Call the existing Bet Builder Calculation API to calculate the Bet Builder odds.
2. When the punter places the bet, call the new Void Recalculation API using the\
   same selections to get the latest price with the precomputed void\
   combination.
3. Store the returned precomputed void combinations together with the\
   original bet.
4. If one selection is later declared void, retrieve the matching precomputed\
   void combination.
5. Use the returned odds to settle the remaining valid selections.

<a href="https://iodocs.betradar.com/?urls.primaryName=Unified%20Feed%20Integration#/CustomBet%20API/calculateProbabilityVoid" class="button primary">Try the API</a>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sportradar.com/uof/custombet-cb/api/void-recalculation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.