For the complete documentation index, see llms.txt. This page is also available as Markdown.

ways_prematch

Goal: Place a ways selection with 3 UF legs (two on the same event, different outcomes, plus one other event) as customer_waysaccepted.

Use Selection.newWaysSelectionBuilder().setSelections(...).

How to build the request (Java SDK)

1

End customer

Set the EndCustomer to customer_ways.

2

Build the ways selection

Create a top-level ways selection with three nested UF legs. Include sr:match:15050881 twice with different outcomes, plus another match.

3

Set the stake and send the ticket

Use a cash stake and call sendTicket.

Java example

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;

UfSelection a = Selection.newUfSelectionBuilder()
    .setProductId("3").setEventId("sr:match:15050881")
    .setMarketId("10").setOutcomeId("o1")
    .setOdds(Odds.newDecimalOddsBuilder().setValue(new BigDecimal("1.38")).build())
    .build();
UfSelection b = Selection.newUfSelectionBuilder()
    .setProductId("3").setEventId("sr:match:15050881")
    .setMarketId("m1").setOutcomeId("o2")
    .setOdds(Odds.newDecimalOddsBuilder().setValue(new BigDecimal("1.38")).build())
    .build();
UfSelection c = Selection.newUfSelectionBuilder()
    .setProductId("3").setEventId("sr:match:44444444")
    .setMarketId("m1").setOutcomeId("o3")
    .setOdds(Odds.newDecimalOddsBuilder().setValue(new BigDecimal("1.38")).build())
    .build();

TicketRequest request = TicketRequest.newBuilder()
    .setTicketId("tid-ways")
    .setContext(TicketContext.newBuilder()
        .setLimitId(123L)
        .setChannel(Channel.newMobileChannelBuilder()
            .setLang("en")
            .setIp("127.0.0.1")
            .setDeviceId("deviceId123")
            .build())
        .setEndCustomer(EndCustomer.newBuilder().setId("customer_ways").build())
        .build())
    .setBets(Bet.newBuilder()
        .setBetId("bet-1")
        .setSelections(Selection.newWaysSelectionBuilder().setSelections(a, b, c).build())
        .setStake(Stake.newCashStakeBuilder().setAmount(new BigDecimal("10")).setCurrency("EUR").build())
        .build())
    .build();
TicketResponse response = mbsSdk.getTicketProtocol().sendTicket(request);
// ACCEPTED

Wire JSON (what the SDK sends)

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_ways"

Mandatory (sandbox)

string

No (routing)

content.bets[].selections[].type

"ways"

Mandatory

string

No (routing)

content.bets[].selections[].selections

(3 UF legs)

Mandatory

array of object

No

content.bets[].stake[].type

"cash"

Mandatory

string

No (routing)

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).

Expected response

Java getter
Expected value

getStatus()

AcceptanceStatus.ACCEPTED

getCode()

0

getMessage()

"accepted" (sandbox)

Common mistakes

Mistake
Result

Wrong customer / selection type

Route mismatch

Missing sandbox match among nested legs

May fail routing

See also: Error responses in the parent manual.

Was this helpful?