Get bet by user reference
User
Get bet by user reference
Look up every bet tied to a client-defined identifier
GET
Get bet by user reference
Look up every bet tied to aDocumentation Index
Fetch the complete documentation index at: https://docs.4casters.io/llms.txt
Use this file to discover all available pages before exploring further.
userReference. userReference is an optional client-defined string you can attach to an order at place time to track it on your side — this endpoint is the read counterpart.
The response separates results into three buckets:
unmatched— open offers from this reference that are still resting on the book.matched— matched (ungraded) bets from this reference.graded— graded (settled) bets from this reference, includingrisk,win,fee, andresult.
Request
GET /user/getBetByUserReference
Client-defined reference passed in at place time.
Scope the lookup to a single game.
Response
Open orders — same shape as Get unmatched orders.
Matched (ungraded) bets — same shape as Get matched bets.
Graded (settled) bets — same shape as Get graded wagers.
Errors
| Status | Meaning |
|---|---|
408 | userReference or gameID missing. |
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 client-defined reference passed in at place time.
A 4casters game id (ObjectID). Get game ids from GET /exchange/v2/getGames or GET /exchange/v2/getOrderbook.
Response
Three-bucket wager view: open (unmatched), filled-but-not-graded (matched), and settled (graded).