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

promo_boosted_odds

Goal: Place an odds-boost selection as customer_promo and receive accepted.

Use Selection.newOddsBoostSelectionBuilder() with a nested UF selection plus boost odds. Wire type "odds-boost".

How to build the request (Java SDK)

1

Set the end customer and cash stake

Use EndCustomer customer_promo and a cash stake.

2

Create the top-level odds-boost selection

Use Selection.newOddsBoostSelectionBuilder() with the nested UF selection and decimal boost odds.

3

Use the required nested UF event

The nested UF selection must use event sr:match:15050881.

4

Send the ticket

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.stake.Stake;
import java.math.BigDecimal;

Selection uf = Selection.newUfSelectionBuilder()
    .setProductId("3").setEventId("sr:match:15050881")
    .setMarketId("m1").setOutcomeId("o1")
    .setOdds(Odds.newDecimalOddsBuilder().setValue(new BigDecimal("2.0")).build())
    .build();

TicketRequest request = TicketRequest.newBuilder()
    .setTicketId("tid-boost")
    .setContext(TicketContext.newBuilder()
        .setLimitId(123L)
        .setChannel(Channel.newMobileChannelBuilder()
            .setLang("en")
            .setIp("127.0.0.1")
            .setDeviceId("deviceId123")
            .build())
        .setEndCustomer(EndCustomer.newBuilder().setId("customer_promo").build())
        .build())
    .setBets(Bet.newBuilder()
        .setBetId("bet-1")
        .setSelections(Selection.newOddsBoostSelectionBuilder()
            .setSelection(uf)
            .setOdds(Odds.newDecimalOddsBuilder().setValue(new BigDecimal("2.5")).build())
            .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_promo"

Mandatory (sandbox)

string

No (routing)

content.bets[].selections[].type

"odds-boost"

Mandatory

string

No (routing)

content.bets[].selections[].selection

nested UF

Mandatory

object

No (event routing via nest)

content.bets[].selections[].odds

boost odds

Mandatory

object

No (echoed)

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

Top-level UF instead of odds-boost

Wrong promo route

Nested event not sandbox match

Route mismatch

See also: Error responses in the parent manual.

Was this helpful?