Pagination
All list endpoints return a unified paginated response shape.
Response Shape
{
"total": 100,
"page": 1,
"page_size": 20,
"items": [...]
}
| Field | Type | Description |
|---|---|---|
total | integer | Total number of records matching the query |
page | integer | Current page number (1-based) |
page_size | integer | Number of items per page |
items | array | Records for the current page |
Request Parameters
Pagination is controlled via query parameters. Note: the size parameter name is inconsistent across endpoints — GET /api/brand/list uses page_size, while all other list endpoints use size.
| Endpoint | Page param | Size param |
|---|---|---|
GET /api/brand/list | page | page_size |
GET /api/player/list | page | size |
GET /api/player/{id}/transactions | page | size |
GET /api/bet/list | page | size |
GET /api/sports-bet/list | page | size |
Defaults and limits
| Parameter | Default | Maximum |
|---|---|---|
page | 1 | — |
size / page_size | 20 | 100 |
Both parameters must be positive integers (>= 1). Passing a value outside the valid range returns a 422 validation error.
Known inconsistency
GET /api/brand/list accepts page_size while all other list endpoints accept size. This inconsistency exists in the current API and will be addressed in a future release.