> 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/mts/features/bet-referral.md).

# Bet Referral

The Bet Referral feature provides clients (bookmakers) with a final layer of decision-making by enabling your trading team to manually review bets that would otherwise be rejected by the standard MTS validation. Integrated directly into the existing Monitoring page via a dedicated Bet Referral widget, this feature allows operators to override liability-based rejections and accept bets that would otherwise be permanently rejected.\
Bet Referral is designed exclusively for use by the client's internal trading team. MTS traders do not\
review or manage these referred bets.

To check the status of a referred bet, the clients use the [Manual review request](/transaction30api/api-description/ticket-json-format-description/manual-review-request.md).

### Ticket acceptance flow

When a bet is initially rejected with an eligible rejection code, it enters a pending state and is displayed within the Bet Referral widget for manual review. See below for the various states a referred bet can go through:

* **Initial Rejection**: The bet is rejected by standard MTS validation with an eligible liability-based\
  rejection code.
* **Pending Referral**: The bet is held for manual review and is displayed in the Bet Referral widget\
  until a trader action is taken or the review time expires.
* **Manually Accepted**: A trader explicitly accepts the bet during the Pending Referral window; the\
  initial rejection is overridden, and an acceptance response is returned to the client.
* **Final Rejected**: The bet is rejected by a Trader; the rejection is confirmed and a final\
  rejection response is returned to the client.
* **Timed Out**: No Trader action is taken before the review time expires; the rejection is confirmed\
  and a final rejection response is returned to the client.

### Rejection codes

Bet Referral is invoked for bets that have been rejected due to specific liability breaches. The eligible\
rejection codes are:

* **-701** (Aggregated Bookmaker & Limit ID Liability)
* **-703** (Bet Level Liability)
* **-704** (Event Level Liability)

### Prerequisites

To utilize Bet Referral, clients must be integrated on the Transaction 3.0 API. This feature is not supported on older API versions.


---

# 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:

```
GET https://docs.sportradar.com/mts/features/bet-referral.md?ask=<question>
```

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.