> 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/transaction30api/sandbox/user-manual/multi_bet.md).

# multi\_bet

**Goal:** Place a ticket with **two bets** as **`customer_multi_bet`** (only this customer allows multi-bet) and receive **accepted** with two `betDetails`.

## How to build the request (Java SDK)

{% stepper %}
{% step %}

## Set the end customer

Use `EndCustomer` **`customer_multi_bet`**.
{% endstep %}

{% step %}

## Create two bets

Create two `Bet` objects, each typically with one UF selection. The first bet's first event should be **`sr:match:15050881`**.
{% endstep %}

{% step %}

## Add cash stakes and send the ticket

Use cash stakes and call `sendTicket`.
{% endstep %}
{% endstepper %}

Other customers with multiple bets hit schema validation (`RESP_ERROR_REPLY`), not the `-999` fallback.

## Java example

```java
import com.sportradar.mbs.sdk.entities.channel.Channel;
import com.sportradar.mbs.sdk.entities.common.AcceptanceStatus;
import com.sportradar.mbs.sdk.entities.common.Bet;
import com.sportradar.mbs.sdk.entities.common.EndCustomer;
import com.sportradar.mbs.sdk.entities.common.TicketContext;
import com.sportradar.mbs.sdk.entities.odds.Odds;
import com.sportradar.mbs.sdk.entities.request.TicketRequest;
import com.sportradar.mbs.sdk.entities.response.TicketResponse;
import com.sportradar.mbs.sdk.entities.selection.Selection;
import com.sportradar.mbs.sdk.entities.selection.UfSelection;
import com.sportradar.mbs.sdk.entities.stake.Stake;
import java.math.BigDecimal;

TicketRequest request = TicketRequest.newBuilder()
    .setTicketId("tid-multi")
    .setContext(TicketContext.newBuilder()
        .setLimitId(123L)
        .setChannel(Channel.newMobileChannelBuilder()
            .setLang("en")
            .setIp("127.0.0.1")
            .setDeviceId("deviceId123")
            .build())
        .setEndCustomer(EndCustomer.newBuilder().setId("customer_multi_bet").build())
        .build())
    .setBets(
        Bet.newBuilder()
            .setBetId("bet-1")
            .setSelections(Selection.newUfSelectionBuilder()
                .setProductId("3").setEventId("sr:match:15050881")
                .setMarketId("m1").setOutcomeId("o1")
                .setOdds(Odds.newDecimalOddsBuilder().setValue(new BigDecimal("2.0")).build())
                .build())
            .setStake(Stake.newCashStakeBuilder().setAmount(new BigDecimal("10")).setCurrency("EUR").build())
            .build(),
        Bet.newBuilder()
            .setBetId("bet-2")
            .setSelections(Selection.newUfSelectionBuilder()
                .setProductId("3").setEventId("sr:match:22222222")
                .setMarketId("m1").setOutcomeId("o1")
                .setOdds(Odds.newDecimalOddsBuilder().setValue(new BigDecimal("2.0")).build())
                .build())
            .setStake(Stake.newCashStakeBuilder().setAmount(new BigDecimal("5")).setCurrency("EUR").build())
            .build())
    .build();
TicketResponse response = mbsSdk.getTicketProtocol().sendTicket(request);
// ACCEPTED; getBetDetails() length 2
```

## Wire JSON (what the SDK sends)

```json
{
  "operatorId": 9985,
  "correlationId": "corr-1",
  "timestampUtc": 1710000000000,
  "operation": "ticket-placement",
  "version": "3.0",
  "content": {
    "type": "ticket",
    "ticketId": "tid-multi",
    "context": {
      "limitId": 123,
      "channel": {
        "type": "mobile",
        "lang": "en",
        "ip": "127.0.0.1",
        "deviceId": "deviceId123"
      },
      "endCustomer": { "id": "customer_multi_bet" }
    },
    "bets": [
      {
        "betId": "bet-1",
        "selections": [{
            "type": "uf",
            "eventId": "sr:match:15050881",
            "marketId": "m1",
            "outcomeId": "o1",
            "productId": "3",
            "odds": { "type": "decimal", "value": "2.0" }
          }],
        "stake": [{ "type": "cash", "amount": "10", "currency": "EUR" }]
      },
      {
        "betId": "bet-2",
        "selections": [{
            "type": "uf",
            "eventId": "sr:match:22222222",
            "marketId": "m1",
            "outcomeId": "o1",
            "productId": "3",
            "odds": { "type": "decimal", "value": "2.0" }
          }],
        "stake": [{ "type": "cash", "amount": "5", "currency": "EUR" }]
      }
    ]
  }
}
```

| Field name                             | Value                  | Mandatory / Optional | Data type       | Ignored by sandbox   |
| -------------------------------------- | ---------------------- | -------------------- | --------------- | -------------------- |
| `operatorId`                           | `9985`                 | Mandatory            | integer         | Yes                  |
| `correlationId`                        | `"corr-1"`             | Mandatory            | string          | No (echoed in reply) |
| `timestampUtc`                         | `1710000000000`        | Mandatory            | integer         | Yes                  |
| `operation`                            | `"ticket-placement"`   | Mandatory            | string          | No                   |
| `version`                              | `"3.0"`                | Mandatory            | string          | No (echoed in reply) |
| `content`                              | *(object)*             | Mandatory            | object          | No                   |
| `content.type`                         | `"ticket"`             | Mandatory            | string          | No                   |
| `content.context`                      | *(object)*             | Mandatory            | object          | No                   |
| `content.context.limitId`              | `123`                  | Mandatory            | integer         | Yes                  |
| `content.context.channel`              | *(object)*             | Mandatory            | object          | Yes                  |
| `content.context.channel.type`         | `"mobile"`             | Mandatory            | string          | Yes                  |
| `content.context.channel.lang`         | `"en"`                 | Mandatory            | string          | Yes                  |
| `content.context.channel.ip`           | `"127.0.0.1"`          | Optional             | string          | Yes                  |
| `content.context.channel.deviceId`     | `"deviceId123"`        | Optional             | string          | Yes                  |
| `content.context.endCustomer`          | *(object)*             | Mandatory (sandbox)  | object          | No                   |
| `content.context.endCustomer.id`       | `"customer_multi_bet"` | Mandatory (sandbox)  | string          | No (routing)         |
| `content.bets`                         | *(2 bets)*             | Mandatory            | array of object | No                   |
| `content.bets[].selections[].type`     | `"uf"`                 | Mandatory            | string          | No (routing)         |
| `content.bets[0].selections[].eventId` | `"sr:match:15050881"`  | Mandatory            | string          | No (routing)         |
| `content.bets[].stake[].type`          | `"cash"`               | Mandatory            | string          | No (routing)         |

{% hint style="info" %}
`endCustomer` / `endCustomer.id` are optional in the Ticket 3.0 schema but **mandatory for this sandbox scenario** (routing). **Ignored by sandbox** means the field is not used for routing and not used when building the reply (schema-only for the WebSocket / Ticket 3.0 envelope).
{% endhint %}

## Expected response

| Java getter       | Expected value                 |
| ----------------- | ------------------------------ |
| `getStatus()`     | `AcceptanceStatus.ACCEPTED`    |
| `getCode()`       | `0`                            |
| `getMessage()`    | `"accepted"` (sandbox)         |
| `getBetDetails()` | Two entries (`bet-1`, `bet-2`) |

```json
{
  "correlationId": "corr-1",
  "timestampUtc": 1710000001000,
  "operation": "ticket-placement",
  "version": "3.0",
  "content": {
    "type": "ticket-reply",
    "ticketId": "tid-multi",
    "status": "accepted",
    "code": 0,
    "message": "accepted",
    "signature": "sandbox-signature",
    "betDetails": [
      {
        "betId": "bet-1",
        "code": 0,
        "message": "accepted",
        "selectionDetails": [{
          "code": 0,
          "message": "accepted [sandbox=customer=customer_multi_bet,oddsFormat=decimal,selection=multi-bet]",
          "selection": {
            "type": "uf",
            "eventId": "sr:match:15050881",
            "marketId": "m1",
            "outcomeId": "o1",
            "productId": "3",
            "odds": { "type": "decimal", "value": "2.0" }
          }
        }]
      },
      {
        "betId": "bet-2",
        "code": 0,
        "message": "accepted",
        "selectionDetails": [{
          "code": 0,
          "message": "accepted",
          "selection": {
            "type": "uf",
            "eventId": "sr:match:22222222",
            "marketId": "m1",
            "outcomeId": "o1",
            "productId": "3",
            "odds": { "type": "decimal", "value": "2.0" }
          }
        }]
      }
    ]
  }
}
```

## Common mistakes

| Mistake                                      | Result                                                       |
| -------------------------------------------- | ------------------------------------------------------------ |
| Multi-bet with a non-`customer_multi_bet` id | Schema validation error (not `-999` fallback)                |
| Only one bet                                 | Still may accept but does not exercise multi-bet reply shape |

See also: [Error responses](broken://pages/3cdf760ce49fd6992d47d7772f4a4b9f67f0519f#error-responses) in the parent manual.


---

# 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/transaction30api/sandbox/user-manual/multi_bet.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.