Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.erysta.com/llms.txt

Use this file to discover all available pages before exploring further.

Welcome to the Erysta API documentation. The Erysta API provides a professional-grade interface for digital gaming partners to access our global catalog and inventory. Built for reliability and ease of integration, our infrastructure allows you to automate procurement and monitor availability with confidence.

​
API Base URLs

The default base endpoint for all API requests is: 
https://api.erysta.com/v1/partners
We recommend using environment variables to manage this URL within your application. This allows your system to remain flexible and adapt to different networking environments without code changes.

​
🇷🇺 Regional Connectivity (Russia)

Due to local network restrictions and web filtering enforced by Roskomnadzor, users or servers located within the Russian Federation may experience connection timeouts or blocks when accessing our primary Cloudflare-routed domain. To ensure stable access, please use our dedicated regional endpoint: 
https://api.erysta.ru/v1/partners
Note: If you continue to experience connectivity issues after switching to the .ru endpoint, please contact our support team for further assistance.

​
Core Principles

The Erysta API is designed around modern standards to ensure a seamless integration experience:
  • RESTful Design: We use standard HTTP verbs (GET, POST, etc.) and response codes.
  • Inventory Synchronization: To ensure data consistency with our global suppliers, inventory levels and pricing are synchronized once or twice per hour.
  • JSON Standard: All data exchange is performed in JSON format for universal compatibility.
  • Security: HTTPS is mandatory for all requests. Plain HTTP connections are strictly prohibited to protect your data.

​
Response Structure

{
  "status": 200,
  "success": true,
  "details": {
    "data": {
       // Requested resources (products, orders, etc.)
    },
    "extensions": {
      "cache": "no-store",
      "trace_id": "req-7f8a9b2c...",
      "timestamp": "2026-03-09T15:30:00.000Z"
    }
  }
}
Key Metadata Fields
  • trace_id: A unique identifier for the request. Always provide this ID when contacting our support team.
  • cache: Indicates if the response was served fresh (no-store) or from our internal cache (HIT).
  • timestamp: The exact time the response was generated in ISO 8601 format.