> ## Documentation Index
> Fetch the complete documentation index at: https://docs.4casters.io/llms.txt
> Use this file to discover all available pages before exploring further.
# 获取已结算注单
> 列出两个日期之间的已结算注单及盈亏汇总
返回调用方在两个日期之间的全部**已结算（已判定）注单**，以及盈亏和成交量汇总。日期对应注单所属赛事的**开赛时间**（因此 `startDate=06-22-2022` 返回开赛时间晚于 06-21-2022 00:00 GMT 的注单）。
请求
`GET /user/getGradedWagers`
开始日期（`MM-DD-YYYY`）。默认为 `10-21-2020`。
结束日期（`MM-DD-YYYY`）。默认为今天。
```bash curl theme={null}
curl "https://api.4casters.io/user/getGradedWagers?startDate=01-01-2024&endDate=02-01-2024" \
-H "Authorization: Bearer YOUR_TOKEN"
```
响应
已结算注单数组，按开赛时间降序排列。
投注 ID。
成交事务 ID。
展示用票据号。
`moneyline`、`spread`、`total` 或 `moneyline1x2`。
`winner`、`loser`、`push` 或 `refund`。
原始投注额。
成交时的美式赔率。
出现在 `spread` 上。
出现在 `total` 上。
出现在 `total` 上。
出现在 `moneyline` 和 `spread` 上。
出现在 `moneyline1x2` 上。
用于 `moneyline1x2` — `yes` 或 `no`。
成交发生的 ISO 8601 时间戳。
注单被判定的 ISO 8601 时间戳。
下单的 ISO 8601 时间戳。
此处始终为 `true`。
订单来源，例如 `api`、`web`、`mobile`。
已撮合部分的风险额（字符串，两位小数）。
扣除佣金后的可赢金额。
已撮合部分收取的佣金。
该注单的净盈亏。亏损为负，盈利为正，走水为 `0`。
成交时可比的 Pinnacle 盘口快照（如有）。
返回注单的汇总合计。
`result` 之和（已四舍五入）。
`min(risk, win)` 之和（已四舍五入）。
示例
```json JSON theme={null}
{
"data": {
"graded": [
{
"id": "64c98e8c0745a206acf18ad7",
"txID": "64c99640453fd2ad91206018",
"ticketNumber": "5a5494406ef9e2c5988b30bf666ce55e",
"type": "total",
"outcome": "loser",
"bet": 1,
"odds": 101,
"total": 8.5,
"OU": "over",
"matchedTime": "2023-08-01T23:33:20.273Z",
"settledAt": "2023-08-02T02:26:16.152Z",
"createdAt": "2023-08-01T23:33:20.273Z",
"graded": true,
"platform": "api",
"risk": "1.01",
"win": "1.00",
"fee": "0.01",
"result": "-1.01",
"pinnacleLine": { "odds": -102, "total": 8.5, "OU": "over" },
"game": {
"id": "64c7fa454803b0ff0f7f5741",
"league": "MLB",
"sport": "baseball",
"start": "2023-08-01T23:45:00.000Z",
"ended": true,
"participants": [/* ... */]
}
}
],
"summary": { "pnl": -1, "volume": 1 }
}
}
```
## OpenAPI
````yaml api-reference/openapi.json GET /user/getGradedWagers
openapi: 3.1.0
info:
title: 4casters REST API
version: 1.0.0
description: >-
Public REST API for the 4casters peer-to-peer betting exchange. Use this API
to manage your account, query the orderbook and games, and place / edit /
cancel orders.
All responses (unless noted otherwise) are JSON envelopes of the form `{
"data": ... }`.
contact:
name: 4casters
url: https://4casters.io
servers:
- url: https://api.4casters.io
description: Production
security:
- bearerAuth: []
tags:
- name: Authentication
description: Login and account session management
- name: User
description: Read account info, bets, and orders
- name: Orders
description: Place, edit, look up, and cancel orders
- name: Markets
description: Browse leagues, games, participants, and orderbooks
- name: Affiliate
description: Affiliate / referral commission
paths:
/user/getGradedWagers:
get:
tags:
- User
summary: Get graded wagers
description: >-
Return all of the caller's graded (settled) wagers between two dates,
plus a summary of P&L and volume. Dates correspond to the **start time
of the game** the wager is on (so `startDate=06-22-2022` returns wagers
on games starting after 06-21-2022 00:00 GMT).
parameters:
- name: startDate
in: query
required: false
description: Start date (`MM-DD-YYYY`). Defaults to `10-21-2020`.
schema:
type: string
example: 01-01-2024
- name: endDate
in: query
required: false
description: End date (`MM-DD-YYYY`). Defaults to today.
schema:
type: string
example: 02-01-2024
responses:
'200':
description: Graded wagers and summary
content:
application/json:
schema:
type: object
properties:
data:
type: object
properties:
graded:
type: array
items:
$ref: '#/components/schemas/GradedWager'
summary:
$ref: '#/components/schemas/GradedSummary'
'401':
$ref: '#/components/responses/Unauthorized'
components:
schemas:
GradedWager:
type: object
description: A settled wager.
properties:
id:
type: string
txID:
type: string
ticketNumber:
type: string
type:
$ref: '#/components/schemas/MarketType'
outcome:
type: string
enum:
- winner
- loser
- push
- refund
bet:
type: number
odds:
type: integer
spread:
type: number
nullable: true
total:
type: number
nullable: true
OU:
type: string
enum:
- over
- under
participantID:
type: string
market:
type: string
side:
$ref: '#/components/schemas/MarketSide'
matchedTime:
type: string
format: date-time
settledAt:
type: string
format: date-time
createdAt:
type: string
format: date-time
graded:
type: boolean
closed:
type: boolean
cancelled:
type: boolean
adminRefund:
type: boolean
platform:
type: string
example: api
fee:
type: string
description: Commission charged on the matched portion.
risk:
type: string
win:
type: string
result:
type: string
description: Net P&L on this wager (signed).
pinnacleLine:
type: object
description: >-
Snapshot of the comparable Pinnacle line at fill time, when
available.
game:
$ref: '#/components/schemas/GameSummary'
GradedSummary:
type: object
properties:
pnl:
type: integer
description: Sum of `result` across the returned wagers (rounded).
volume:
type: integer
description: Sum of `min(risk, win)` across the returned wagers (rounded).
MarketType:
type: string
enum:
- moneyline
- spread
- total
- moneyline1x2
description: >-
Market type. `moneyline1x2` is **soccer-only** (three-way money line:
home / away / draw).
MarketSide:
type: string
description: |-
Order side. Meaning depends on `type`:
- `moneyline`, `spread` — the participant id you are backing.
- `total` — `"over"` or `"under"`.
- `moneyline1x2` — `"yes"` or `"no"` on the outcome named by `market`.
GameSummary:
type: object
properties:
id:
type: string
league:
type: string
sport:
type: string
start:
type: string
format: date-time
ended:
type: boolean
eventName:
type: string
nullable: true
isFutures:
type: boolean
participants:
type: array
items:
$ref: '#/components/schemas/Participant'
Participant:
type: object
properties:
id:
type: string
longName:
type: string
shortName:
type: string
homeAway:
type: string
enum:
- home
- away
mainPitcher:
type: string
nullable: true
rotationNumber:
type: string
nullable: true
futuresSide:
type: string
nullable: true
score:
type: number
description: Final score; only present for ended games.
responses:
Unauthorized:
description: Missing or invalid auth token
securitySchemes:
bearerAuth:
type: http
scheme: bearer
description: >-
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.
````
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.