Reporting API
Read-only calls for your back office: your casino settings, GGR figures to reconcile with your own books, and your transaction log. They are independent of the game flow — nothing here is needed to launch games or answer callbacks.
| Call | Method | Returns |
|---|---|---|
| Casinos | GET | your casinos and their settings, secrets masked |
| GGR Summary | POST | bets, wins and GGR of a period, per currency |
| Transactions | POST | the bet, win and cancel calls of your casino, a page at a time |
Authentication
The same as every API Method: your AUTH_TOKEN in the
X-API-KEY header, from an IP on your casino’s allow-list.
X-API-KEY: {AUTH_TOKEN}- Only your own casinos can be read. A
casino_idthat is not yours is answered withHTTP 400. - A casino whose allow-list does not contain the calling IP is answered with
HTTP 403. casino_idis a single integer — a list of ids is rejected withHTTP 400. Call once per casino.
Rate limit
The three calls share one limit per AUTH_TOKEN: 30 calls a minute, counted
in fixed one-minute windows. Every response carries the current state:
| Header | Description |
|---|---|
X-RateLimit-Limit | calls allowed per minute |
X-RateLimit-Remaining | calls left in the current minute |
Retry-After | only on HTTP 429: seconds until the next call is accepted |
Beyond the limit the call is answered with HTTP 429 Too Many Requests. Wait for
Retry-After seconds before calling again.
The limit is generous for normal use: reading a busy casino’s whole day of
transactions takes about 25 pages of 1000 rows.
Pace bulk downloads instead of retrying on 429.
Errors
These calls do not use the wallet error codes. A failed call
is answered with an HTTP error status and a JSON body whose message tells what
went wrong:
{
"name": "Bad Request",
"message": "Invalid parameter: casino_id",
"code": 0,
"status": 400
}| Status | When |
|---|---|
400 | missing or invalid parameter, a casino_id that is not yours, a body that is not a JSON object |
401 | missing or wrong X-API-KEY |
403 | the calling IP is not allow-listed, or the data is not enabled for the casino |
405 | wrong HTTP method (for example GET on a POST call) |
429 | rate limit exceeded, see Rate limit |