Getting Started
Welcome to the Client Reports API. This guide will help you make your first API call in minutes.
Get Your Client Secret
Your client secret is a UUID that uniquely identifies your operator account. To obtain one:
- Contact your account manager or the platform support team.
- You will receive a UUID in the format:
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. - Store it securely — treat it like a password.
WARNING
Your client secret grants full access to your reporting data. Never expose it in client-side code, public repositories, or URLs.
Base URL
All API requests are made to:
https://api.syssoft1.comAuthentication
Every request must include your client secret in the X-Client-Secret header:
X-Client-Secret: your-uuid-secret-hereSee the Authentication page for detailed information.
Common Headers
Include these headers in every request:
| Header | Value | Required |
|---|---|---|
X-Client-Secret | Your UUID secret | Yes |
Accept | application/json | Yes |
Rate Limiting
The API enforces a limit of 60 requests per minute per client secret. If you exceed this limit, you will receive a 429 Too Many Requests response. See Error Handling for more details.
Quick Start — Your First Request
Get your latest transactions with a simple curl command:
curl -X GET 'https://api.syssoft1.com/api/client/reports/transactions?page=1&filter[per_page]=10' \
-H 'Accept: application/json' \
-H 'X-Client-Secret: your-uuid-secret-here'A successful response looks like this:
{
"data": [
{
"id": 12345,
"type": "DEBIT",
"amount": 10.00,
"currency": "USD",
"player": "player123",
"provider": "Pragmatic Play",
"game": "Sweet Bonanza",
"created_at": "2026-04-13 10:30:00"
}
],
"pagination": {
"current_page": 1,
"total": 150,
"per_page": 10,
"total_pages": 15
},
"totals": { ... }
}Available Endpoints
| Endpoint | Description |
|---|---|
GET /api/client/reports/transactions | Transaction history with filters and aggregated totals |
GET /api/client/reports/daily-games | Game performance rankings with tier system |
GET /api/client/reports/players | Player analytics with activity and profitability data |
Next Steps
- Read the Authentication guide for security best practices.
- Explore the API Reference for detailed endpoint documentation.
- Review Error Handling to understand how errors are returned.
- Check the Glossary for terminology used in the API.