Get bet by wager request ID
User
Get bet by wager request ID
Look up every bet derived from a single place request
GET
Get bet by wager request ID
Look up every bet tied to a singleDocumentation Index
Fetch the complete documentation index at: https://docs.4casters.io/llms.txt
Use this file to discover all available pages before exploring further.
wagerRequestID. A wagerRequestID is server-generated for each order in a place request — use it to tie together every fill and resting offer that resulted from a single submitted order.
The response separates results into three buckets:
unmatched— open offers from the request that are still resting on the book. Always empty for this endpoint — use Get bet by user reference instead if you need open offers in the response.matched— matched (ungraded) bets from the request.graded— graded (settled) bets from the request, includingrisk,win,fee, andresult.
Request
GET /user/getBetByWagerRequestID
The
wagerRequestID returned by /session/v3/place (in either the matched[].wagerRequestID or unmatched.wagerRequestID field).Response
Empty array.
Matched (ungraded) bets — same shape as Get matched bets.
Graded (settled) bets — same shape as Get graded wagers.
Errors
| Status | Meaning |
|---|---|
400 | wagerRequestID is missing or unknown. |
Authorizations
Pass your auth token in the Authorization header. The Bearer prefix is optional; the server also accepts a signed auth cookie or a token field in the request body.
Query Parameters
The wagerRequestID returned by /session/v3/place.
Response
Three-bucket wager view: open (unmatched), filled-but-not-graded (matched), and settled (graded).