rejected_odds_too_high

Goal: Place a normal-looking UF single with elevated decimal odds and receive rejected -421 (Odds value is too high).

How to build the request (Java SDK)

1

Use the same shell as single_accepted

Use the same shell as single_accepted, but set the EndCustomer ID to customer_rejected_4xx.

2

Set elevated decimal odds

Set decimal odds to an elevated value, for example 100.

3

Use a cash stake and send the ticket

Use a cash stake, then 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;

TicketRequest request = TicketRequest.newBuilder()
    .setTicketId("Ticket_rej_4xx")
    .setContext(TicketContext.newBuilder()
        .setLimitId(123L)
        .setChannel(Channel.newMobileChannelBuilder()
            .setLang("en")
            .setIp("127.0.0.1")
            .setDeviceId("deviceId123")
            .build())
        .setEndCustomer(EndCustomer.newBuilder()
            .setId("customer_rejected_4xx")
            .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("100"))
                .build())
            .build())
        .setStake(Stake.newCashStakeBuilder()
            .setAmount(new BigDecimal("10"))
            .setCurrency("EUR")
            .build())
        .build())
    .build();

TicketResponse response = mbsSdk.getTicketProtocol().sendTicket(request);
// expect: response.getStatus() == AcceptanceStatus.REJECTED, getCode() == -421

Wire JSON (what the SDK sends)

The SDK produces a Ticket 3.0 envelope around the ticket content. Example JSON (envelope IDs may differ because the SDK generates correlationId / timestampUtc):

{
  "operatorId": 9985,
  "correlationId": "corr-1",
  "timestampUtc": 1710000000000,
  "operation": "ticket-placement",
  "version": "3.0",
  "content": {
    "type": "ticket",
    "ticketId": "Ticket_rej_4xx",
    "context": {
      "limitId": 123,
      "channel": {
        "type": "mobile",
        "lang": "en",
        "ip": "127.0.0.1",
        "deviceId": "deviceId123"
      },
      "endCustomer": {
        "id": "customer_rejected_4xx"
      }
    },
    "bets": [
      {
        "betId": "bet-1",
        "selections": [
          {
            "type": "uf",
            "eventId": "sr:match:15050881",
            "marketId": "m1",
            "outcomeId": "o1",
            "productId": "3",
            "odds": {
              "type": "decimal",
              "value": "100"
            }
          }
        ],
        "stake": [
          {
            "type": "cash",
            "amount": "10",
            "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.ticketId	"Ticket_rej_4xx"	Mandatory	string	No (echoed in reply)
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_rejected_4xx"	Mandatory (sandbox)	string	No (routing)
content.bets	(1 bet)	Mandatory	array of object	No
content.bets[].betId	"bet-1"	Optional	string	No (echoed in reply)
content.bets[].selections	(1 selection)	Mandatory	array of object	No
content.bets[].selections[].type	"uf"	Mandatory	string	No (routing)
content.bets[].selections[].eventId	"sr:match:15050881"	Mandatory	string	No (routing)
content.bets[].selections[].marketId	"m1"	Mandatory	string	No (routing)
content.bets[].selections[].outcomeId	"o1"	Mandatory	string	No (routing)
content.bets[].selections[].productId	"3"	Mandatory	string	No (routing)
content.bets[].selections[].odds	(object)	Mandatory	object	No
content.bets[].selections[].odds.type	"decimal"	Mandatory	string	No (routing)
content.bets[].selections[].odds.value	"100"	Mandatory	string	No (echoed in reply)
content.bets[].stake	(1 stake)	Mandatory	array of object	No
content.bets[].stake[].type	"cash"	Mandatory	string	No (routing)
content.bets[].stake[].amount	"10"	Mandatory	string	Yes
content.bets[].stake[].currency	"EUR"	Mandatory	string	Yes

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

On the Java client, assert against TicketResponse:

Java getter	Expected value
getStatus()	AcceptanceStatus.REJECTED
getCode()	-421
getMessage()	"Odds value is too high"
getTicketId()	"Ticket_rej_4xx" (echo)

Wire JSON (content type "ticket-reply"; fields live under content, not content.ticket):

{
  "correlationId": "corr-1",
  "timestampUtc": 1710000001000,
  "operation": "ticket-placement",
  "version": "3.0",
  "content": {
    "type": "ticket-reply",
    "ticketId": "Ticket_rej_4xx",
    "status": "rejected",
    "code": -421,
    "message": "Odds value is too high",
    "signature": "sandbox-signature",
    "betDetails": [
      {
        "betId": "bet-1",
        "code": -421,
        "message": "Odds value is too high",
        "selectionDetails": [
          {
            "code": -421,
            "message": "Odds value is too high [oddsValue='100']",
            "selection": {
              "type": "uf",
              "eventId": "sr:match:15050881",
              "marketId": "m1",
              "outcomeId": "o1",
              "productId": "3",
              "odds": {
                "type": "decimal",
                "value": "100"
              }
            }
          }
        ]
      }
    ]
  }
}

Common mistakes

Mistake	Result
Wrong EndCustomer.setId (not "customer_rejected_4xx")	Different scenario or fallback
Wrong event / odds / stake shape	Route mismatch / fallback

See also: Error responses in the parent manual.