rejected_ticket_exception

Goal: Send a schema-valid single UF ticket and receive rejected with code -205 (Invalid prefix or incorrect market pattern).

How to build the request (Java SDK)

1

Build TicketRequest with a unique ticketId

2

Configure TicketContext

Set limitId to 123, use a mobile Channel, and set the EndCustomer id to customer_rejected_2xx.

3

Add one bet with one UF selection

Use sr:match:15050881 with the demo invalid pattern:

• productId: "55"
• outcomeId: "~1"
• Decimal odds

4

Add a cash stake and send the ticket

Send the request with mbsSdk.getTicketProtocol().sendTicket(request).

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_2xx")
    .setContext(TicketContext.newBuilder()
        .setLimitId(123L)
        .setChannel(Channel.newMobileChannelBuilder()
            .setLang("en")
            .setIp("127.0.0.1")
            .setDeviceId("deviceId123")
            .build())
        .setEndCustomer(EndCustomer.newBuilder()
            .setId("customer_rejected_2xx")
            .build())
        .build())
    .setBets(Bet.newBuilder()
        .setBetId("bet-1")
        .setSelections(Selection.newUfSelectionBuilder()
            .setProductId("55")
            .setEventId("sr:match:15050881")
            .setMarketId("1")
            .setOutcomeId("~1")
            .setOdds(Odds.newDecimalOddsBuilder()
                .setValue(new BigDecimal("1.32"))
                .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() == -205

Wire JSON

The SDK produces a Ticket 3.0 envelope around the ticket content. Envelope ids may differ because the SDK generates correlationId and timestampUtc.

{
  "operatorId": 9985,
  "correlationId": "corr-1",
  "timestampUtc": 1710000000000,
  "operation": "ticket-placement",
  "version": "3.0",
  "content": {
    "type": "ticket",
    "ticketId": "Ticket_rej_2xx",
    "context": {
      "limitId": 123,
      "channel": {
        "type": "mobile",
        "lang": "en",
        "ip": "127.0.0.1",
        "deviceId": "deviceId123"
      },
      "endCustomer": {
        "id": "customer_rejected_2xx"
      }
    },
    "bets": [
      {
        "betId": "bet-1",
        "selections": [
          {
            "type": "uf",
            "eventId": "sr:match:15050881",
            "marketId": "1",
            "outcomeId": "~1",
            "productId": "55",
            "odds": {
              "type": "decimal",
              "value": "1.32"
            }
          }
        ],
        "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_2xx"	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_2xx"	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	"1"	Mandatory	string	No (echoed in reply)
content.bets[].selections[].outcomeId	"~1"	Mandatory	string	No (echoed in reply)
content.bets[].selections[].productId	"55"	Mandatory	string	No (echoed in reply)
content.bets[].selections[].odds	(object)	Mandatory	object	No
content.bets[].selections[].odds.type	"decimal"	Mandatory	string	No (routing)
content.bets[].selections[].odds.value	"1.32"	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 and 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()	-205
getMessage()	"Invalid prefix or incorrect market pattern"
getTicketId()	"Ticket_rej_2xx" (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_2xx",
    "status": "rejected",
    "code": -205,
    "message": "Invalid prefix or incorrect market pattern",
    "signature": "sandbox-signature",
    "betDetails": [
      {
        "betId": "bet-1",
        "code": -205,
        "message": "Invalid prefix or incorrect market pattern",
        "selectionDetails": [
          {
            "code": -205,
            "message": "Invalid prefix or incorrect market pattern [marketPattern productId='55' outcomeId='~1']",
            "selection": {
              "type": "uf",
              "eventId": "sr:match:15050881",
              "marketId": "1",
              "outcomeId": "~1",
              "productId": "55",
              "odds": {
                "type": "decimal",
                "value": "1.32"
              }
            }
          }
        ]
      }
    ]
  }
}

Common mistakes

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

See also: Error responses in the parent manual.