Skip to main content

Bet-Ledger APIs

Make Bet Offer

info

This request must have the authorization header. Refer to Authorization method guide for more details

Request

PropertyValue
methodPOST
url$baseUrl/bets/make-offer
Content-Typeapplication/json

Body

PropertyTypeRequiredDefaultDescription
wager_referencestringYes-Wager reference
requesting_oddsnumber (>=1)Yes-Requesting odds
requesting_amountnumber (>0)Yes-Requesting amount
requesting_user_idnumberNo-Requesting user id
requesting_user_referencestringNo-Requesting user reference
allowed_acceptor_idsnumber[]No-Array of user IDs allowed to accept this bet
allowed_acceptor_referencesstring[]No-Array of user references allowed to accept this bet
metaobjectNo-User specified meta data
info

Either the requesting_user_id or requesting_user_reference must be provided

Allowed Acceptors

You can restrict who can accept your bet offer by providing either allowed_acceptor_ids or allowed_acceptor_references. If both are provided, users matching either condition can accept the bet.

If no allowed acceptor fields are provided, the bet offer will be open to all users.

# Open bet offer (anyone can accept)
curl -X POST "$baseUrl/bets/make-offer" \
-H "Content-Type: application/json" \
-d '{
"wager_reference": "example_wager_reference",
"requesting_odds": 2,
"requesting_amount": 100,
"requesting_user_id": 12345
}'

# Restricted bet offer (only specific users can accept)
curl -X POST "$baseUrl/bets/make-offer" \
-H "Content-Type: application/json" \
-d '{
"wager_reference": "example_wager_reference",
"requesting_odds": 2,
"requesting_amount": 100,
"requesting_user_id": 12345,
"allowed_acceptor_ids": [67890, 11111],
"allowed_acceptor_references": ["user_abc", "user_xyz"]
}'

Response

Http Code: 201

{
"data": {
"bet_id": 2,
"wager_reference": "wager-4",
"wager_id": 2
},
"message": "Bet offer placed successfully"
}

Accept Bet Offer

info

This request must have the authorization header. Refer to Authorization method guide for more details

Request

PropertyValue
methodPOST
url$baseUrl/bets/accept-offer
Content-Typeapplication/json

Body

PropertyTypeRequiredDefaultDescription
wager_referencestringNo-Wager reference
bet_idnumberNo-Bet ID (alternative to wager_reference)
maximum_oddsnumber (>=1)Yes-Requesting odds
accepting_amountnumber (>0)Yes-Requesting amount
accepting_user_idnumberNo-Accepting user id
accepting_user_referencenumberNo-Accepting user reference
requesting_user_idnumberNo-Requesting user id
requesting_user_referencenumberNo-Requesting user reference
metajsonNo-User specified meta data
info

Either the accepting_user_id or accepting_user_reference must be provided to specify requesting user.

info

Either the requesting_user_id or requesting_user_reference can be provided to specify requesting user. If both are omitted, the system would accept bets matching any user.

note

Either wager_reference or bet_id must be provided. If bet_id is specified, the wager_reference field will be ignored.

# Using wager_reference
curl -X POST "$baseUrl/bets/accept-offer" \
-H "Content-Type: application/json" \
-d '{
"wager_reference": "example_wager_reference",
"maximum_odds": 2,
"accepting_amount": 100,
"accepting_user_id": 12345,
"meta": {}
}'

# Using bet_id (wager_reference will be ignored)
curl -X POST "$baseUrl/bets/accept-offer" \
-H "Content-Type: application/json" \
-d '{
"bet_id": 456,
"maximum_odds": 2,
"accepting_amount": 100,
"accepting_user_id": 12345,
"meta": {}
}'

Response

Http Code: 201

{
"data": [
{
"bet_id": 2,
"requesting_user_reference": "a4_user_2YRDqo69dO4DGdin",
"requesting_user_id": 4,
"accepted_amount": 300,
"accepted_odds": 3,
"wager_reference": "wager-4",
"wager_id": 2
}
],
"message": "Bet offer accepted successfully"
}

Open Bets

info

This request must have the authorization header. Refer to Authorization method guide for more details

Request

PropertyValue
methodGET
url$baseUrl/bets/open-bets
Content-Typeapplication/json

Query Params

PropertyTypeRequiredDefaultDescription
pagenumberNo1Current page
per_pagenumberNo20Number of items per page
wager_referencesstringNo-Comma separated wager references
account_idsnumber(comma separated)No-Comma separated account ids
requesting_user_idsnumber(comma separated)No-Comma separated requesting user ids
requesting_user_referencesstring(comma separated)No-Comma separated requesting user references
created_afternumber(timestamp) | DateStringNo-Filter result from this date
created_beforenumber(timestamp) | DateStringNo-Filter result to this date
minimum_oddsnumberNo1Minimum odds
maximum_oddsnumberNo-Maximum odds
minimum_amountnumberNo-Minimum amount
maximum_amountnumberNo-Maximum amount
sort_by"requesting_odds" | "requesting_amount" | "created_at"No"created_at"Sort by
sort_direction"asc" | "desc"No"asc"Sort direction
info

user_ids and user_references can be used in combination. The results would be merged

curl -X GET "$baseUrl/bets/open-bets" \
-H "Content-Type: application/json" \
-G \
--data-urlencode "page=1" \
--data-urlencode "per_page=20" \

Response

Http Code: 200

{
"data": [
{
"id": 3,
"account_id": 4,
"offer_status": "requesting",
"wager_id": 2,
"wager_reference": "wager-4",
"requesting_user_id": 4,
"requesting_user_reference": "a4_user_2YRDqo69dO4DGdin",
"requesting_odds": 3,
"requesting_amount": 300,
"allowed_acceptor_ids": [67890, 11111],
"created_at": "2025-03-11T16:11:08.156Z"
}
],
"per_page": 20,
"page": 1,
"total": 1,
"from": 1,
"to": 1,
"last_page": 1,
"total_requesting_amount": 300
}

Bet History

info

This request must have the authorization header. Refer to Authorization method guide for more details

Request

PropertyValue
methodGET
url$baseUrl/bets/history
Content-Typeapplication/json

Query Params

PropertyTypeRequiredDefaultDescription
pagenumberNo1Current page
per_pagenumberNo20Number of items per page
wager_referencesstringNo-Comma separated wager references
account_idsnumber(comma separated)No-Comma separated account ids
user_idsnumber(comma separated)No-Comma separated user ids
user_referencesstring(comma separated)No-Comma separated user references
bet_outcomes"undecided" | "win" | "loss" | "push" | "half-win" | "half-loss" | "void"No-Comma separated bet outcomes
created_afternumber(timestamp) | DateStringNo-Filter result from this date
created_beforenumber(timestamp) | DateStringNo-Filter result to this date
include_bet_trailsbooleanNofalseInclude bet trails in response
include_bet_trails_transactionsbooleanNofalseInclude bet trail transactions
sort_by"effective_odds" | "effective_amount" | "created_at"No"created_at"Sort by
sort_direction"asc" | "desc"No"asc"Sort direction
info

user_ids and user_references can be used in combination. The results would be merged

curl -X GET "$baseUrl/bets/history" \
-H "Content-Type: application/json" \
-G \
--data-urlencode "page=1" \
--data-urlencode "per_page=20" \
--data-urlencode "sort_by=created_at" \
--data-urlencode "sort_direction=asc"

Response

Http Code: 200

{
"data": [
{
"id": 2,
"requesting_user_id": 4,
"requesting_user_reference": "a4_user_2YRDqo69dO4DGdin",
"accepting_user_id": 4,
"accepting_user_reference": "a4_user_2YRDqo69dO4DGdin",
"offer_status": "accepted",
"effective_amount": 300,
"effective_odds": 3,
"override_outcome": null,
"is_active": true,
"created_at": "2025-03-11T15:50:33.601Z",
"wager": {
"id": 2,
"reference": "wager-4",
"outcome": "undecided",
"account_id": 4,
"created_at": "2025-03-11T15:50:33.601Z",
"updated_at": "2025-03-11T15:50:33.601Z"
},
"bet_trails": [
{
"id": 4,
"bet_id": 2,
"account_id": 4,
"wager_id": 2,
"offer_status": "requesting",
"description": "Requesting for bet",
"outcome": "undecided",
"override_outcome": null,
"requesting_odds": 3,
"requesting_amount": 300,
"accepting_odds": null,
"accepting_amount": null,
"effective_odds": null,
"effective_amount": null,
"created_at": "2025-03-11T15:50:33.601Z",
"transactions": []
},
{
"id": 6,
"bet_id": 2,
"account_id": 4,
"wager_id": 2,
"offer_status": "accepted",
"description": "Bet offer accepted",
"outcome": "undecided",
"override_outcome": null,
"requesting_odds": 3,
"requesting_amount": 300,
"accepting_odds": 3,
"accepting_amount": 300,
"effective_odds": null,
"effective_amount": null,
"created_at": "2025-03-11T16:20:43.304Z",
"transactions": []
}
]
},
{
"id": 3,
"requesting_user_id": 4,
"requesting_user_reference": "a4_user_2YRDqo69dO4DGdin",
"accepting_user_id": null,
"accepting_user_reference": null,
"offer_status": "requesting",
"effective_amount": null,
"effective_odds": null,
"override_outcome": null,
"is_active": true,
"created_at": "2025-03-11T16:11:08.156Z",
"wager": {
"id": 2,
"reference": "wager-4",
"outcome": "undecided",
"account_id": 4,
"created_at": "2025-03-11T15:50:33.601Z",
"updated_at": "2025-03-11T15:50:33.601Z"
},
"bet_trails": [
{
"id": 5,
"bet_id": 3,
"account_id": 4,
"wager_id": 2,
"offer_status": "requesting",
"description": "Requesting for bet",
"outcome": "undecided",
"override_outcome": null,
"requesting_odds": 3,
"requesting_amount": 300,
"accepting_odds": null,
"accepting_amount": null,
"effective_odds": null,
"effective_amount": null,
"created_at": "2025-03-11T16:11:08.156Z",
"transactions": []
}
]
}
],
"per_page": 20,
"page": 1,
"total": 2,
"from": 1,
"to": 2,
"last_page": 1
}
Field Description

is_active: A boolean field indicating whether the bet is currently active or inactive. Active bets (true) can be accepted by other users and appear in open bet listings. Inactive bets (false) cannot be accepted and are excluded from open bet results.

Update wager outcome

info

This request must have the authorization header. Refer to Authorization method guide for more details

Request

PropertyValue
methodPOST
url$baseUrl/bets/update-wager-outcome
Content-Typeapplication/json

Body

PropertyTypeRequiredDefaultDescription
referencestringYes-Wager reference
outcome"undecided" | "win" | "loss" | "push" | "half-win" | "half-loss" | "void"Yes-Bet outcomes
curl -X POST "$baseUrl/bets/update-wager-outcome" \
-H "Content-Type: application/json" \
-d '{
"reference": "example_wager_reference",
"outcome": "win"
}'

Response

Http Code: 201

{
"message": "Wager outcome updated successfully"
}

Cancel Bet Offer

info

This request must have the authorization header. Refer to Authorization method guide for more details

Request

PropertyValue
methodPOST
url$baseUrl/bets/cancel-offer
Content-Typeapplication/json

Body

PropertyTypeRequiredDefaultDescription
requesting_user_idnumberNo-Requesting user id
requesting_user_referencestringNo-Requesting user reference
wager_referencesstring[]No[]Array of wager references to target
bet_idnumberNo-Bet ID (alternative to wager_references)
cancel_amountnumberNo-Specific amount to cancel (partial cancel)
cancel_allbooleanNofalseCancel all matching bets
minimum_oddsnumberNo-Only cancel bets with odds >= this value
maximum_oddsnumberNo-Only cancel bets with odds <= this value
info

Either the requesting_user_id or requesting_user_reference must be provided to identify the requesting user.

info

Either cancel_amount must be provided OR cancel_all must be set to true. If both are provided, cancel_all takes precedence.

note

Either wager_references array or bet_id must be provided. If bet_id is specified, odds filtering (minimum_odds, maximum_odds) is ignored and the specific bet is targeted regardless of its odds.

Important Notes
  • Only open (requesting status) bets can be canceled
  • Accepted bets cannot be canceled
  • Partial cancellation creates a new bet for the remaining amount
  • User exposure is automatically reduced by the canceled amount
  • All cancellations are recorded in the bet trail for audit purposes
  • Odds filtering: Use minimum_odds and/or maximum_odds to target specific bet ranges
  • Wager references: Multiple wager references can be processed in a single request
  • Bet ID priority: When bet_id is provided, odds filters are ignored
# Cancel specific amount using wager references
curl -X POST "$baseUrl/bets/cancel-offer" \
-H "Content-Type: application/json" \
-d '{
"requesting_user_reference": "user123",
"wager_references": ["wager456", "wager789"],
"cancel_amount": 150
}'

# Cancel specific amount using bet ID (ignores odds filters)
curl -X POST "$baseUrl/bets/cancel-offer" \
-H "Content-Type: application/json" \
-d '{
"requesting_user_id": 123,
"bet_id": 789,
"cancel_amount": 50
}'

# Cancel all bets with odds filtering
curl -X POST "$baseUrl/bets/cancel-offer" \
-H "Content-Type: application/json" \
-d '{
"requesting_user_reference": "user123",
"wager_references": ["wager456"],
"cancel_all": true,
"minimum_odds": 2.0,
"maximum_odds": 4.0
}'

# Cancel bets above minimum odds only
curl -X POST "$baseUrl/bets/cancel-offer" \
-H "Content-Type: application/json" \
-d '{
"requesting_user_reference": "user123",
"wager_references": ["wager456", "wager789"],
"cancel_all": true,
"minimum_odds": 2.5
}'

Response

Single bet cancellation
Http Code: 201

{
"message": "Bet offer canceled successfully",
"data": [
{
"bet_id": 123,
"wager_reference": "wager456",
"wager_id": 2
}
]
}

Multiple bets cancellation with odds filtering
Http Code: 201

{
"message": "Bet offer canceled successfully",
"data": [
{
"bet_id": 123,
"wager_reference": "wager456",
"wager_id": 2
},
{
"bet_id": 124,
"wager_reference": "wager456",
"wager_id": 2
},
{
"bet_id": 125,
"wager_reference": "wager789",
"wager_id": 3
}
]
}

Partial cancellation (creates new bet for remaining amount)
Http Code: 201

{
"message": "Bet offer canceled successfully",
"data": [
{
"bet_id": 126,
"wager_reference": "wager456",
"wager_id": 2,
"note": "Partial cancellation - remaining amount: 50"
}
]
}

Override Bet Outcome

info

This request must have the authorization header. Refer to Authorization method guide for more details

Request

PropertyValue
methodPOST
url$baseUrl/bets/override-outcome
Content-Typeapplication/json

Body

PropertyTypeRequiredDefaultDescription
bet_idnumberYes-Bet ID to override
override_outcome"undecided" | "win" | "loss" | "push" | "half-win" | "half-loss" | "void"Yes-Override bet outcome
curl -X POST "$baseUrl/bets/override-outcome" \
-H "Content-Type: application/json" \
-d '{
"bet_id": 123,
"override_outcome": "win"
}'

Response

Http Code: 200

{
"message": "Bet outcome override updated successfully"
}

Batch Bet Operations (Atomic)

info

This request must have the authorization header. Refer to Authorization method guide for more details.

Execute multiple bet operations in a single atomic transaction. If any operation fails, the entire batch is rolled back and NO operation is applied.

Request

PropertyValue
methodPOST
url$baseUrl/bets/batch
Content-Typeapplication/json

Atomic Behavior

  • All operations are validated first (structure, uniqueness, user existence, odds, exposure).
  • Exposure / balance checks are performed considering the cumulative effect of the whole batch.
  • If ANY operation fails validation or business logic, the entire batch aborts (no partial updates).
  • A successful batch returns HTTP 201.
  • A failed batch returns HTTP 400 (or other appropriate error) with no side-effects.
  • There is NO HTTP 207 (partial success) for this endpoint.

Body

FieldTypeRequiredDescription
operationsArray<BatchOperation>YesOrdered list of operations to execute atomically

BatchOperation Type

type BatchOperation = {
operation_type: "make_bet_offer" | "accept_bet_offer" | "cancel_bet_offer" | "update_wager_outcome" | "override_bet_outcome";
operation_id: string;
data: object; // Corresponds to the request body of the individual endpoint
}
FieldTypeRequiredDescription
operation_typestringYesOne of allowed enum values (below)
operation_idstringYesClient-supplied unique identifier within the batch
dataobjectYesOperation payload - corresponds to the request body of the individual endpoint for that operation type
Data Field Correspondence

The data object for each operation type corresponds exactly to the request body parameters of the individual API endpoints:

Duplicate operation_id values cause the entire batch to fail.

Supported operation_type Values

Enum ValueDescription
make_bet_offerCreate a new bet offer (requesting state)
accept_bet_offerAccept (match) existing requesting offers
cancel_bet_offerCancel open bet offers (requesting state)
update_wager_outcomeDecide a wager's outcome
override_bet_outcomeOverride an accepted bet's outcome

Operation Payload Schemas (data)

1. make_bet_offer

FieldTypeRequiredNotes
requesting_user_idnumberNoRequired if requesting_user_reference absent
requesting_user_referencestringNoRequired if requesting_user_id absent
wager_referencestringNoRequired if bet_id absent
bet_idnumberNoAlternative to wager_reference (takes precedence if both)
requesting_oddsnumber (>=1)YesDecimal odds
requesting_amountnumber (>0)YesStake amount
metaobjectNoArbitrary metadata (string:string)

2. accept_bet_offer

FieldTypeRequiredNotes
accepting_user_idnumberNoRequired if accepting_user_reference absent
accepting_user_referencestringNoRequired if accepting_user_id absent
requesting_user_idnumberNoOptional filter (only accept from this user id)
requesting_user_referencestringNoOptional filter (only accept from this user reference)
wager_referencestringNoRequired if bet_id absent
bet_idnumberNoAlternative to wager_reference (takes precedence)
maximum_oddsnumber (>=1)YesReject if matched odds exceed this
accepting_amountnumber (>0)YesAmount to accept
metaobjectNoArbitrary metadata

3. cancel_bet_offer

FieldTypeRequiredNotes
requesting_user_idnumberNoRequired if requesting_user_reference absent
requesting_user_referencestringNoRequired if requesting_user_id absent
wager_referencesstring[]NoRequired if bet_id absent
bet_idnumberNoTargets one specific bet (odds filters ignored)
cancel_amountnumber (>0)NoPartial cancellation amount
cancel_allbooleanNoIf true, cancels all matching amounts
minimum_oddsnumber (>=1.01)NoOnly cancel odds >= value (ignored if bet_id)
maximum_oddsnumber (>=1.01)NoOnly cancel odds <= value (ignored if bet_id)

Constraints:

  • Provide either cancel_amount OR cancel_all: true.
  • Provide wager_references or bet_id.
  • Only requesting (open) offers are cancelable.
  • Partial cancellation leaves remaining amount as a new or adjusted open bet.

4. update_wager_outcome

FieldTypeRequiredNotes
referencestringYesWager reference
outcome"undecided" | "win" | "loss" | "push" | "half-win" | "half-loss" | "void"YesNew outcome

5. override_bet_outcome

FieldTypeRequiredNotes
bet_idnumberYesAccepted bet id
override_outcome"undecided" | "win" | "loss" | "push" | "half-win" | "half-loss" | "void"YesOverride outcome
Operation Requirements
  • Make Offer: Either requesting_user_id or requesting_user_reference required
  • Accept Offer: Either accepting_user_id or accepting_user_reference required
  • Cancel Bet Offer: requesting_user_id and wager_references are required, plus either cancel_amount or cancel_all
  • Update Wager Outcome: reference and outcome are both required
  • Override Bet Outcome: bet_id and override_outcome are both required
Batch Operation Notes
  • Atomic guarantee: zero side-effects on any failure.
  • Exposure computation: Cumulative across all operations in batch
  • Unique operation IDs: Must be unique within the batch
  • Sequential processing: Operations processed in array order
  • Validation: Each operation validated separately before execution
  • Error isolation: Any single failure aborts entire batch
curl -X POST "$baseUrl/bets/batch" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_TOKEN" \
-d '{
"operations": [
{
"operation_type": "make_bet_offer",
"operation_id": "offer-1",
"data": {
"requesting_user_id": 101,
"requesting_odds": 2.0,
"requesting_amount": 100,
"wager_reference": "atomic-wager-1"
}
},
{
"operation_type": "accept_bet_offer",
"operation_id": "accept-1",
"data": {
"accepting_user_id": 102,
"wager_reference": "atomic-wager-1",
"maximum_odds": 2.2,
"accepting_amount": 50
}
},
{
"operation_type": "cancel_bet_offer",
"operation_id": "cancel-1",
"data": {
"requesting_user_id": 101,
"wager_references": ["atomic-wager-1"],
"cancel_amount": 25,
"minimum_odds": 1.8
}
},
{
"operation_type": "update_wager_outcome",
"operation_id": "decide-1",
"data": {
"reference": "atomic-wager-1",
"outcome": "win"
}
}
]
}'

Response

All operations successful
Http Code: 201

{
"message": "All batch operations completed successfully",
"results": [
{
"operation_id": "offer-1",
"operation_type": "make_bet_offer",
"success": true,
"data": {
"bet_id": 1201,
"wager_reference": "atomic-wager-1",
"wager_id": 501
}
},
{
"operation_id": "accept-1",
"operation_type": "accept_bet_offer",
"success": true,
"data": [
{
"bet_id": 1201,
"requesting_user_id": 101,
"accepted_amount": 50,
"accepted_odds": 2.0,
"wager_reference": "atomic-wager-1",
"wager_id": 501
}
]
},
{
"operation_id": "cancel-1",
"operation_type": "cancel_bet_offer",
"success": true,
"data": [
{
"bet_id": 1203,
"wager_reference": "atomic-wager-1",
"wager_id": 501
}
]
},
{
"operation_id": "decide-1",
"operation_type": "update_wager_outcome",
"success": true,
"message": "Wager outcome updated successfully"
}
]
}

Common Failure Reasons

ScenarioError Snippet
Over-exposure"would cause negative effective balance"
Duplicate IDs"Operation IDs must be unique within a batch"
Missing user identifiers"must be defined"
Invalid odds/value"must not be less than"
Nothing to cancel"No cancelable bets found"
Wager already decided"Wager has already been decided"
Override invalid state"bet offer status must be 'accepted'"
Performance Benefits

Batch operations provide several advantages:

  • Reduced Network Overhead: Multiple operations in a single HTTP request
  • Atomic Transaction Processing: All-or-nothing guarantee maintains data consistency
  • Cumulative Exposure Validation: Balance checks consider the entire batch effect
  • Better Error Management: Single point of failure with detailed error information
  • Improved Throughput: Ideal for high-frequency trading and bulk operations
Important Notes
  • Atomic guarantee: zero side-effects on any failure.
  • No partial success: Unlike some batch APIs, this endpoint never applies partial results
  • Exposure is computed cumulatively: multiple make/accept operations may jointly exceed limits.
  • Use unique, meaningful operation_id values for reliable correlation.
  • bet_id overrides wager_reference when both are present (in supported operations).
  • Cancel logic ignores odds filters when bet_id is supplied.

Get Single Bet

info

This request must have the authorization header. Refer to Authorization method guide for more details

Request

PropertyValue
methodGET
url$baseUrl/bets/:id
Content-Typeapplication/json

Query Params

PropertyTypeRequiredDefaultDescription
include_bet_trailsbooleanNofalseInclude bet trails in response
include_bet_trails_transactionsbooleanNofalseInclude bet trail transactions
curl -X GET "$baseUrl/bets/123" \
-H "Content-Type: application/json"

Response

Http Code: 200

{
"data": {
"id": 2,
"requesting_user_id": 4,
"requesting_user_reference": "a4_user_2YRDqo69dO4DGdin",
"accepting_user_id": 4,
"accepting_user_reference": "a4_user_2YRDqo69dO4DGdin",
"offer_status": "accepted",
"effective_amount": 300,
"effective_odds": 3,
"override_outcome": null,
"is_active": true,
"created_at": "2025-03-11T15:50:33.601Z",
"wager": {
"id": 2,
"reference": "wager-4",
"outcome": "undecided",
"account_id": 4,
"created_at": "2025-03-11T15:50:33.601Z",
"updated_at": "2025-03-11T15:50:33.601Z"
},
"bet_trails": [
{
"id": 4,
"bet_id": 2,
"account_id": 4,
"wager_id": 2,
"offer_status": "requesting",
"description": "Requesting for bet",
"outcome": "undecided",
"override_outcome": null,
"requesting_odds": 3,
"requesting_amount": 300,
"accepting_odds": null,
"accepting_amount": null,
"effective_odds": null,
"effective_amount": null,
"created_at": "2025-03-11T15:50:33.601Z",
"transactions": []
},
{
"id": 6,
"bet_id": 2,
"account_id": 4,
"wager_id": 2,
"offer_status": "accepted",
"description": "Bet offer accepted",
"outcome": "undecided",
"override_outcome": null,
"requesting_odds": 3,
"requesting_amount": 300,
"accepting_odds": 3,
"accepting_amount": 300,
"effective_odds": null,
"effective_amount": null,
"created_at": "2025-03-11T16:20:43.304Z",
"transactions": []
}
]
},
"message": "Bet retrieved successfully"
}
Field Description

is_active: A boolean field indicating whether the bet is currently active or inactive. Active bets (true) can be accepted by other users and appear in open bet listings. Inactive bets (false) cannot be accepted and are excluded from open bet results.