Search bet history

POST /bet/search/

Operation ID: search_bets

Filter and search bet history using multiple criteria by providing specific bet IDs.

Request Body

{
  "ids": [123, 456, 789]
}

Parameters

Field	Type	Required	Description
ids	array[integer]	No	List of bet IDs to retrieve

Response

Success Response (200)

Returns an array of BetHistorySimple objects:

[
  {
    "id": 123,
    "transaction_min_created_at": "2024-01-24T20:59:19.440549+11:00",
    "display_name": "My Bot Account",
    "amount": 10.00,
    "current_odds": 2.25,
    "created_at": "2024-01-24T20:59:19.440549+11:00",
    "meeting_date": "2024-01-24",
    "market": "Fixed Win",
    "submit_time": "2024-01-24T21:00:00+11:00",
    "result_time": "2024-01-24T21:10:00+11:00",
    "submit_result": "Success",
    "submit_error": null,
    "profit": -10.00,
    "used_boost": false,
    "used_spg": false,
    "used_bonus": false,
    "transaction_id": "TXN123",
    "bot_id": "BOT001",
    "is_deleted": false,
    "notified": true,
    "reporting_usage": 10.00,
    "sports": "RACING",
    "profit_updated_by": "system",
    "profit_updated_at": "2024-01-24T21:15:00+11:00",
    "settled_at": "2024-01-24T21:10:00+11:00",
    "transaction_result": "LOSS",
    "status": "SETTLED",
    "status_notes": "Race completed",
    "label": "Strategy A",
    "owner": 612,
    "bookie": 42,
    "notification": 789
  }
]

Error Responses

• 500 Internal server error - Server encountered an error processing the request

Usage

Search for Specific Bets:

curl -X POST "https://betmatic.app/api/bet/search/" \
  -H "Content-Type: application/json" \
  -H "Authorization: Token your_token" \
  -d '{
    "ids": [123, 456, 789]
  }'

Search for Single Bet:

curl -X POST "https://betmatic.app/api/bet/search/" \
  -H "Content-Type: application/json" \
  -H "Authorization: Token your_token" \
  -d '{
    "ids": [123]
  }'

Potential Use Cases

1. Specific Bet Analysis: Retrieve detailed information for particular bets of interest

2. Batch Bet Retrieval: Get multiple specific bets in a single API call for efficiency

3. Bet Verification: Verify specific bet details for reconciliation purposes

4. Performance Analysis: Analyze specific bets that performed well or poorly

5. Reporting: Generate reports for specific sets of bets

6. Audit Purposes: Retrieve specific bets for compliance or audit requirements

7. Customer Support: Look up specific bet details for customer inquiries

8. Data Export: Extract specific bet data for external analysis tools

Authentication

This endpoint requires authentication. Include your token in the Authorization header:

Authorization: Token your_token

Response Schema

Status Code 200

Name	Type	Description
id	integer	Bet History Id used in this system
display_name	string	name of session which placed bet
amount	integer	actual amount that placed, this can be different from notification amount.
current_odds	string	odds that actually applied
created_at	string(date-time)	Time when History is created
market	string	finally placed market
submit_time	string or null	bet slip submit clicked time
result_time	string or null	bet slip submit result time
submit_result	string	result of bet Success or Error or In Review
submit_error	string	If success Accepted, else error string from the bookie
profit	integer	profit obtained from right bet
used_boost	boolean	if this bet is boosted one
used_spg	boolean	if spg is used
used_bonus	boolean	if bonus money is used
transaction_id	integer	to be used to update the accepted amount and odds later
bot_id	string	Id of bot notification sent to
is_deleted	boolean	if bet history is deleted
notified	boolean	if this bet is notified via socket
reported_usage	integer	reported turnover of this bet
sports	string	Type of Sport
owner	integer	users id who placed this bet
bookie	integer	bookie id on whom bet is placed
notification	integer	notification id used in system