Skip to main content
The PlayStarters integration is split into two complementary APIs:
APIDirectionPurpose
Operator APIYour backend → PlayStartersFetch providers, list games, generate game launch URLs.
Seamless Wallet APIPlayStarters → Your backendRead player balance and process financial transactions (BET, WIN, VOID) during gameplay.

​
Operator API

You call PlayStarters’ REST endpoints to integrate the catalog and game launch into your site.
  • Base URL — https://api.playstarters.com
  • Authentication — Authorization: ApiKey ps_<your_api_key> header.
  • Format — JSON request and response bodies.
See Authentication and the Operator API reference: Providers, Games, Launch.

​
Seamless Wallet API

You expose a single POST endpoint that PlayStarters calls during gameplay.
  • Base URL — provided by you (e.g. https://api.yoursite.com/wallet-callback).
  • Authentication — PlayStarters sends Authorization: Bearer <your_wallet_key> (agreed during setup).
  • HTTP method — always POST.
  • Operation type — identified by the type field in the request body (BALANCE, BET, WIN, VOID).
Every successful response must return HTTP 200 OK with the updated balance: 
{ "balance": 100.50 }
See the Wallet API reference: Overview, Balance, Transactions, Idempotency.

​
Currency and amounts

  • Amounts are decimal numbers in the player’s wallet currency (e.g. 10.0, 150.50).
  • The currency field uses ISO 4217 codes (e.g. EUR, USD, BRL).
  • Player and transaction IDs are strings (UUIDs from PlayStarters, your own player IDs are passed back unchanged).
Keep your API key and wallet key secret at all times. Never expose them in client-side code, public repositories, or browser-accessible configuration files.
Reliability note:
Playstarters does not implement automatic retries with backoff.

If your wallet endpoint returns an error (non-2xx) or times out (> 10 seconds), the error is propagated to the game provider.

The provider may retry according to its own policy. Your wallet endpoint must be idempotent (via request_id) to safely handle provider-level retries.