# Custom Bet
Custom Bet is an add-on betting product that allows MTS clients to offer accumulator bets on matches that would otherwise be blocked due to the related contingencies rule.
As an extension for its customers, Unified Odds Feed provides two additional API endpoints that offer information for creating custom-tailored bets for a specific match. Custom Bet allows combining a wide range of betting markets into a single odds and probabilities calculation, much like an accumulator (a single wager made up of multiple selections).
An example of a Custom Bet could include a combination of the following markets:
* Liverpool to win the match
* Liverpool to score the most goals in the first half
* Liverpool to score the most goals in the second half
* Liverpool to win corner 1x2
* Total over 2.5
This means that a combination of markets in a single bet (generally rejected because of the related contingencies rule) is possible.
{% hint style="info" %}
**Note**
* Custom Bet exposes API endpoints and Sportradar currently provides one UI widget. In general, the front-end has to be taken care of by the client.
* The list of Custom Bet supported sports is available [here](https://docs.sportradar.com/mts/features/spaces/1KlIQPveu0EGYCTI8DL1/pages/0PHzgX5a6AUmbcUNKUm3#id-wip-custombetapidocumentationredesign-2.supportedsports-and-markets).
* The functionality is available to UOF clients with an active “Custom Bet” package.
* The UOF Custom Bet API returns a list of all available combinable markets. It is the responsibility of the client to filter out the markets they wish to make available to their end-customers.
{% endhint %}
Custom Bet documentation is available [here](/uof/custombet-cb.md).
XSD files for Custom Bet can be found [here](/uof/xml-schema-definition.md).
The market overview for Custom Bet and Unified Odds Feed can be found [here](/uof/introduction/market-overview-uof-and-cb.md).
### Ticket Acceptance Flow
A client has to send a request using the UOF Custom Bet API to obtain a list of combinable markets and then present this list to the bettor. Once the bettor has picked the selections they wish to bet on, the client has to send another request, this time to obtain consolidated odds for the specified selections.
Once the odds are received, the client sends a Ticket Placement Request to MTS. The request should contain one or more selections of "type":"uf-custom-bet" (including the received odds), each containing up to 10 selections of "type":"uf" (for the selected markets). For more information about composing a ticket request and nesting selections of different types, please see the [Ticket Placement Request](/transaction30api/api-description/ticket-json-format-description/ticket-placement-request.md) description.
Instead of checking individual selection markets and odds, MTS will send a Custom Bet request with the same set of markets to Custom Bet API and the bet will be validated against the response.
**Multi-Event Custom Bet**\
For Soccer Pre-match and Soccer Live, MTS supports Multi-Event Custom Bet functionality. This functionality allows the customer to place a custom bet containing selections from up to 5 different events (as opposed to the single-event custom bet, where all selections relate to the same event). The workflow remains the same as for the single-event custom bet. The bettor selects up to 10 selections (which can be from different events), the customer uses the UOF API and retrieves their consolidated custom bet odds, and finally sends a Ticket Placement Request containing the selections and consolidated odds
**Rejection codes for failed validation cases:**
* -440: for cases where MTS does not receive a response from the Custom Bet API (the customer does not have an active Custom Bet package, markets are no longer active, the event is no longer active, etc.),
* -441: for cases where the odds received in the ticket are higher than those received in the repeated Custom Bet request response.
* -442: external Custom Bet API service is not available
Ticket example with a Custom Bet can be found [here.](/mts/transaction-3.0-api/mts-related-transaction-examples/bet-types-examples-singles-accumulators-custom-bets.../single-custom-bet-on-soccer-with-three-selections.md)
---
# Agent Instructions: 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:
```
GET https://docs.sportradar.com/mts/features/custom-bet.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.