> 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/single_live_async.md). # single\_live\_async **Goal:** Place a **live** UF single (`productId` `"1"`) as **`customer_live_async_accepted`** and receive an immediate reply with code **202** / message **PENDING**. About \~3s later the sandbox logs an ACCEPTED ticket-reply JSON (no second SDK response). ## How to build the request (Java SDK) {% stepper %} {% step %} ## Use the same shell as [`single_accepted`](broken://pages/e84b9421dafc72a9793b6db53513e5046ff022e6) Set the `EndCustomer` ID to **`customer_live_async_accepted`**. {% endstep %} {% step %} ## Select the live UF event Use productId **`"1"`**, eventId **`sr:match:15050881`**, and decimal odds. {% endstep %} {% step %} ## Send a cash stake ticket Use a cash stake and call `sendTicket`. {% endstep %} {% endstepper %} ## 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.stake.Stake; import java.math.BigDecimal; TicketRequest request = TicketRequest.newBuilder() .setTicketId("tid-live-async") .setContext(TicketContext.newBuilder() .setLimitId(123L) .setChannel(Channel.newMobileChannelBuilder() .setLang("en") .setIp("127.0.0.1") .setDeviceId("deviceId123") .build()) .setEndCustomer(EndCustomer.newBuilder() .setId("customer_live_async_accepted") .build()) .build()) .setBets(Bet.newBuilder() .setBetId("bet-1") .setSelections(Selection.newUfSelectionBuilder() .setProductId("1") .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()) .build(); TicketResponse response = mbsSdk.getTicketProtocol().sendTicket(request); // AcceptanceStatus has no PENDING enum — assert getCode() == 202 and getMessage() equals "PENDING" ``` ## 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-live-async", "context": { "limitId": 123, "channel": { "type": "mobile", "lang": "en", "ip": "127.0.0.1", "deviceId": "deviceId123" }, "endCustomer": { "id": "customer_live_async_accepted" } }, "bets": [ { "betId": "bet-1", "selections": [ { "type": "uf", "eventId": "sr:match:15050881", "marketId": "m1", "outcomeId": "o1", "productId": "1", "odds": { "type": "decimal", "value": "2.0" } } ], "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` | `"tid-live-async"` | 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_live_async_accepted"` | 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 (echoed in reply) | | `content.bets[].selections[].outcomeId` | `"o1"` | Mandatory | string | No (echoed in reply) | | `content.bets[].selections[].productId` | `"1"` | Mandatory | string | No (live echo; not a routing facet) | | `content.bets[].selections[].odds.type` | `"decimal"` | Mandatory | string | No (routing) | | `content.bets[].selections[].odds.value` | `"2.0"` | 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 | {% 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 | | --------------- | -------------------------------------------------------------------------------------------- | | `getCode()` | `202` | | `getMessage()` | `"PENDING"` | | `getTicketId()` | `"tid-live-async"` (echo) | | `getStatus()` | No `PENDING` on `AcceptanceStatus` — do not assert ACCEPTED/REJECTED for the immediate reply | Wire JSON (Ticket 3.0 shape). Schema requires `status`; sandbox may omit a meaningful ACCEPTED/REJECTED mapping for this pending reply — prefer asserting `code` / `message`: ```json { "correlationId": "corr-1", "timestampUtc": 1710000001000, "operation": "ticket-placement", "version": "3.0", "content": { "type": "ticket-reply", "ticketId": "tid-live-async", "code": 202, "message": "PENDING", "signature": "sandbox-signature", "betDetails": [ { "betId": "bet-1", "code": 202, "message": "PENDING", "selectionDetails": [ { "code": 202, "message": "PENDING", "selection": { "type": "uf", "eventId": "sr:match:15050881", "marketId": "m1", "outcomeId": "o1", "productId": "1", "odds": { "type": "decimal", "value": "2.0" } } } ] } ] } } ``` {% hint style="info" %} \~3 seconds later the sandbox **logs** an ACCEPTED ticket-reply JSON. That is not delivered as a second `sendTicket` / gRPC response to the SDK client. {% endhint %} ## Common mistakes | Mistake | Result | | ------------------------------------------------------------ | -------------------------------------------- | | productId still `"3"` | May not match live async expectations / echo | | Wrong customer id | Different scenario or fallback | | Asserting `AcceptanceStatus.ACCEPTED` on the immediate reply | Immediate reply is PENDING (code 202) | 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/single_live_async.md?ask=&goal= ``` `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.