Tournament Platform API

The Tournament Platform provides comprehensive REST APIs for integrating real-time multiplayer tournaments into casino systems and game platforms. Our APIs are designed for reliability, scalability, and ease of integration.

API Overview

The Tournament Platform offers two distinct API sets:

Casino Integration APIs

External APIs for casino systems to manage tournaments, players, and results

Game Platform APIs

Internal APIs for game platforms to handle authentication, rooms, and events

Base URL

Production Environment

https://ts.playservices.tech/api

This is the production Tournament Platform API. Use appropriate testing strategies and start with small-scale tournaments during initial integration.

Authentication

The Tournament Platform uses Bearer Token authentication with different API keys for different integration types:

Casino Integration (External APIs)

API Key Format: sk_live_... (production)
Usage: Tournament management, player registration, results retrieval
Permissions: Operator-specific access to tournaments and players

curl -H "Authorization: Bearer sk_live_your_casino_api_key_here" \
  https://ts.playservices.tech/api/tournaments

Game Platform (Internal APIs)

API Key Format: internal_...
Usage: JWT validation, room management, tournament configuration
Permissions: Access to internal game-specific endpoints

curl -H "Authorization: Bearer internal_your_game_platform_key" \
  https://ts.playservices.tech/api/internal/auth/validate-token

Keep your API keys secure and never expose them in client-side code. API keys provide access to sensitive tournament and player data.

Rate Limiting

The Tournament Platform enforces rate limits to ensure service reliability:

API Type	Rate Limit	Burst Limit
Casino Integration	1000 requests/minute	100 requests/10s
Game Platform	5000 requests/minute	500 requests/10s
Webhooks	No limit	-

When you exceed rate limits, you’ll receive a 429 Too Many Requests response with a Retry-After header indicating when to retry.

Request/Response Format

Content Type

All API endpoints accept and return application/json. Always include the Content-Type header in POST/PUT requests:

curl -X POST \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{"name": "Daily Championship"}' \
  https://ts.playservices.tech/api/tournaments

Response Structure

All API responses follow a consistent format: Success Response (200-299):

{
  "tournamentId": "12345",
  "name": "Daily Championship",
  "status": "scheduled",
  ...
}

Error Response (400-599):

{
  "error": "tournament_not_found",
  "message": "Tournament with ID 12345 does not exist",
  "details": {
    "tournamentId": "12345",
    "timestamp": "2024-01-15T20:30:00Z"
  }
}

Error Handling

HTTP Status Codes

Code	Description	Common Causes
`200`	Success	Request completed successfully
`201`	Created	Resource created (tournaments, players)
`400`	Bad Request	Invalid request parameters or format
`401`	Unauthorized	Invalid or missing API key
`403`	Forbidden	API key lacks required permissions
`404`	Not Found	Tournament, player, or resource not found
`409`	Conflict	Resource conflict (duplicate registration)
`429`	Too Many Requests	Rate limit exceeded
`500`	Internal Server Error	Temporary server issue

Error Codes

Common error codes and their meanings:

Error Code	Description	Resolution
`invalid_api_key`	API key format invalid	Check key format and environment
`tournament_not_found`	Tournament doesn’t exist	Verify tournament ID
`player_already_registered`	Player already in tournament	Check existing registrations
`tournament_full`	Max players reached	Increase limit or use waiting list
`insufficient_balance`	Player lacks funds	Verify account balance
`tournament_started`	Cannot modify active tournament	Only modify before start

Pagination

List endpoints support pagination using limit and offset parameters:

GET /api/tournaments?limit=50&offset=100

Response includes pagination metadata:

{
  "tournaments": [...],
  "pagination": {
    "total": 1247,
    "limit": 50,
    "offset": 100,
    "hasMore": true
  }
}

Filtering & Sorting

Most list endpoints support filtering and sorting:

GET /api/tournaments?status=in_progress&gameSlug=crash-classic&sort=createdAt:desc

Common filter parameters:

status - Filter by tournament status
gameSlug - Filter by game type
startDate / endDate - Filter by date range
minPlayers / maxPlayers - Filter by player count

Event Notifications

The Tournament Platform sends real-time tournament event notifications via SQS transport. Webhook endpoints are configured at the transport level, not via API.

Event Documentation

Complete guide to tournament event handling and SQS integration

SDKs & Libraries

Official SDKs are available for popular programming languages:

JavaScript/Node.js

npm install @tournament-platform/js-sdk

PHP

composer require tournament-platform/php-sdk

Python

pip install tournament-platform-sdk

Interactive API Explorer

Use the interactive API explorer below to test endpoints with your API keys:

The API explorer uses the OpenAPI specification to provide real-time API testing. Use appropriate testing strategies when working with the production API.

Common Workflows

1. Tournament Creation & Management

Create Tournament - Set up new tournament
Update Tournament - Modify before start
List Tournaments - View all tournaments
Get Tournament - Retrieve details

2. Player Registration & Management

Register Player - Add player to tournament
Process Rebuy - Handle additional entries
List Players - View tournament participants

3. Results & Leaderboards

Get Leaderboard - Real-time rankings
Get Results - Final tournament results
Player History - Historical performance

4. Game Platform Integration

Validate JWT - Authenticate player access
Get Config - Retrieve tournament settings
Report Events - Send game events

Support & Resources

API Status

Check real-time API availability and performance

Developer Support

Get help with integration questions

Testing Guide

Testing strategies and debugging tools

Best Practices

Security and integration best practices

API Changelog

Stay updated on API changes and new features:

v1.0.0 (Current) - Initial release with full tournament management
All breaking changes will be announced 30 days in advance
Deprecated endpoints will be supported for 6 months minimum

Subscribe to our developer newsletter for API updates and new feature announcements.

​Tournament Platform API

​API Overview

Casino Integration APIs

Game Platform APIs

​Base URL

​Production Environment

​Authentication

​Casino Integration (External APIs)

​Game Platform (Internal APIs)

​Rate Limiting

​Request/Response Format

​Content Type

​Response Structure

​Error Handling

​HTTP Status Codes

​Error Codes

​Pagination

​Filtering & Sorting

​Event Notifications

Event Documentation

​SDKs & Libraries

JavaScript/Node.js

PHP

Python

​Interactive API Explorer

​Common Workflows

​1. Tournament Creation & Management

​2. Player Registration & Management

​3. Results & Leaderboards

​4. Game Platform Integration

​Support & Resources

API Status

Developer Support

Testing Guide

Best Practices

​API Changelog

Tournament Platform API

API Overview

Base URL

Production Environment

Authentication

Casino Integration (External APIs)

Game Platform (Internal APIs)

Rate Limiting

Request/Response Format

Content Type

Response Structure

Error Handling

HTTP Status Codes

Error Codes

Pagination

Filtering & Sorting

Event Notifications

SDKs & Libraries

Interactive API Explorer

Common Workflows

1. Tournament Creation & Management

2. Player Registration & Management

3. Results & Leaderboards

4. Game Platform Integration

Support & Resources

API Changelog