Introduction

Welcome to 7SoftTech Seamless API documentation!

Terms

Before integration

1. Provide your Project Name and WALLET_URL to us.
2. PROVIDER_URL, WALLET_URL, CASINO_ID and AUTH_TOKEN will be provided by one of our managers.

Security

Every request between the two servers is authenticated with an API key. You receive your key (AUTH_TOKEN) from us together with the rest of your credentials, before the integration starts.

• Send the key in the X-API-KEY header of every request, in both directions — the calls the casino makes to PROVIDER_URL and the callbacks the game provider makes to WALLET_URL.

X-API-KEY: {AUTH_TOKEN}

• Validate the header on every incoming request. If it is missing or does not match the expected key, the receiving server (game provider and wallet alike) should respond with HTTP 403 Forbidden.
• The key is a shared secret: keep it server-side only, never expose it to the player’s browser or to the game client. If it leaks, ask us for a new one.

Request and response format

• API Methods are called by the casino on PROVIDER_URL. rungame, create-freespins and cancel-freespins are POST requests with a JSON object body; the rest are GET requests with query parameters.
• API Callbacks are called by the game provider on WALLET_URL as GET requests with query parameters.
• Every response, in both directions, is a JSON object.
• Monetary values use two different units, so watch out when mapping them:
  • callback amount and balance fields are decimal values in the major currency unit (for example 0.25 = 25 cents),
  • the Gift Spin bet parameter is an integer in cents.
• Every callback must return either the documented success payload or an error response.

Workflow