System generated unique id on our side. (will be used in searching in reports)
Only one generated bet id will be created per bet
|
| betId | string | Unique id of the bet |
| betStatusId | int | See [Bet Status](/odds-feed-documentation/placement-validation/dictionary.md#bet-status) for more details. |
| betStatusName | string | See [Bet Status](/odds-feed-documentation/placement-validation/dictionary.md#bet-status) for more details. |
| stake | decimal | Amount the player placed on a bet |
| betSelections | List\ | See [Selection Model](#bet-selection-response-model) for more details |
### Bet Selection Response Model
| Name | Type | Description |
| ------------------- | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| statusCode | int | Determines if the selection is valid or not
See Status Code for more details
|
| message | string | Show the reason the message is invalid or shows a successful message.
See Status Code for more details
|
| fixtureSpecifier | string | Unique id of the fixture |
| marketSpecifier | string | Unique market specifier |
| marketTemplateId | string | Template id of the market |
| selectionTemplateId | string | Template id of the selection |
| odds | decimal | Odds on when the bet was placed |
### Callback
Once the bet placement request has been internally processed and is valid, the API sends a response to a callback URL provided by the client. This callback response contains information about the status of the request.
* Running status: if the request is accepted and processed successfully, the callback response will include a status of "Running". This indicates that the bet placement or cashout request has been successfully executed.
* Rejected status: if the request is rejected due to validation errors or other issues, the callback response will include a status of "Rejected". This indicates that the bet placement or cashout request could not be processed as requested.
### Callback URL Setup
To allow us to deliver data, you need to setup your own API endpoint that exposes the following route:
Endpoint: /bet/status/placement\
Method: POST
The payload request should contain JSON data structured according to the API specifications. Here's an example of a payload request:
```
{
"generatedBetId": "2C922B2D-7F97-4DB5-6203-08DCC7478FE2",
"betId": "7B337436-1A5F-42D7-0DBC-08DCC62915EA",
"betStatusId": 2000,
"betStatusName": "Running",
"reason": "1024 - Ticket accepted (MTS)",
"action": "PLACEBET",
"timestamp": "2024-08-28T09:55:37.2566921Z",
"betSelections": [
{
"marketTemplateId": "223",
"selectionTemplateId": "1714",
"odds": 1.78,
"fixtureSpecifier": "sr:match:52861055",
"marketSpecifier": "hcp=4.5"
}
]
}
```
Properties:
| Name | Type | Description |
| -------------- | -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| betId | string | Unique id of the bet |
| generatedBetId | string | System generated unique id on our side. (will be used in searching in reports)
Only one generated bet id will be created per bet
|
| betStatusId | int | See [Bet Status](/odds-feed-documentation/placement-validation/dictionary.md#bet-status) for more details. |
| betStatusName | string | See [Bet Status](/odds-feed-documentation/placement-validation/dictionary.md#bet-status) for more details. |
| reason | string | Reason why the bet was accepted or rejected. |
| action | string | for the Bet Placement validation, the value would always be "PLACEBET". |
| timestamp | datetime | Timestamp on when the bet was accepted or rejected. |
| betSelections | List\ | See [SelectionRequest Model](#bet-selection-request-model-1) for more details |
### Bet Selection Request Model
| Name | Type | Description |
| ------------------- | ------- | --------------------------------- |
| MarketTemplateId | string | Template id of the market |
| SelectionTemplateId | string | Template id of the selection |
| Odds | decimal | Odds on when the bet was accepted |
| FixtureSpecifier | string | Unique id of the fixture |
| MarketSpecifier | string | Unique id of the market |
| SelectionSpecifier | string | Unique id of the selection |
Once we receive a response from your endpoint, the payload response should contain a JSON data structure as shown in below:
Code: *200 (OK)*
```
{
"statusId": 1000,
"message": "Success"
}
```
Properties:
| Name | Type | Description |
| -------- | ----------------- | ---------------------------------------------------------------- |
| statusId | int | Indicates the status of the request
1000 - Success
|
| message | string (optional) | status message |
Code: *Bad Request (400)*
```
{
"statusId": 1003,
"message": "Error encountered when placing a bet"
}
```
Properties
| Name | Type | Description |
| -------- | ------ | ------------------------------------------------------------------------------ |
| statusId | int | Indicates the status of the request
1003 - Internal Server Error
|
| message | string | status message (you can place here what is the error encountered) |
---
# Agent Instructions: 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:
```
GET https://flyingcockatoo.gitbook.io/odds-feed-documentation/placement-validation/bet-placement-api.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.