Games from Sinatra

Games from Sinatra

Overview

The Sinatra platform serves as the central repository for all game-related data within the Tech Fusion ecosystem. It provides comprehensive information about available games, their providers, technical specifications, and marketing materials. Casino operators use these APIs to:

• Retrieve an up-to-date catalog of available games
• Access marketing materials for promoting games
• Retrieve detailed game history for player activity
• View round details for auditing and support purposes

System Architecture

Sinatra functions as a separate service within the Tech Fusion platform, requiring its own authentication flow. All requests to Sinatra APIs must include a valid JWT token obtained through the login process.

Authentication Process

Before accessing any Sinatra APIs, you must authenticate and obtain a JWT token:

Authentication Prerequisites

1. Login Credentials: You need valid Sinatra user credentials (email and password) provided by Tech Fusion during onboarding
2. JWT Token: After successful login, the system returns a jwt-auth header containing your authentication token
3. Request Headers: This jwt-auth token must be included in all subsequent requests to Sinatra APIs

Available Operations

The Sinatra platform provides the following API endpoints:

Typical Integration Flow

A typical integration with the Sinatra platform follows this workflow:

1. Authentication: Login to obtain JWT token
2. Game Discovery:
   • Retrieve available game providers
   • Retrieve complete game catalog
3. Marketing Integration:
   • Retrieve game marketing assets for website display
4. Player History Access:
   • Retrieve game history for player activity tracking
   • Retrieve round details for dispute resolution

Implementation Best Practices

When integrating with the Sinatra APIs, follow these guidelines:

1. Token Management:

   • Store the JWT token securely
   • Implement token refresh logic to handle expirations
   • Never expose the token to client-side code

2. Data Caching:

   • Cache game catalog and provider data to reduce API calls
   • Implement periodic refreshes (e.g., daily) to ensure data accuracy
   • Always fetch fresh history data to ensure accuracy

3. Error Handling:

   • Implement proper error handling for authentication failures
   • Handle API rate limits gracefully
   • Provide meaningful error messages to operators and support staff

4. Performance Optimization:

   • Use paginated endpoints for large data sets
   • Implement efficient filtering on the client side
   • Minimize API calls during peak usage periods

Next Steps

Begin your integration with the Login User endpoint to obtain authentication credentials, then explore the game catalog and history endpoints based on your implementation requirements.