1. Create your key
Sign in to the developer portal after your subscription is active. Give the key a label, create it and copy the full value before leaving. It is displayed once. Save it in a server environment variable or secret manager. Do not put it in public client code, a repository, screenshots or support messages.
For browser tools, enter the key in Your Access to unlock the math lab, operator sandbox and scripted reviews. The browser unlock lasts up to eight hours. The license and key must both remain active.
2. Start a development session
Your account owns the development wallet. Call the bridge from your backend using x-sr-api-key. Use the returned token with subsequent round and history requests. This example selects Outlaw’s Go Wild; an empty JSON object selects Dead Voltage.
POST https://staticroit.dev/api/developer/platform/launch
Content-Type: application/json
x-sr-api-key: YOUR_PRIVATE_DEVELOPER_KEY
{"gameId":"outlaws-go-wild"}The response includes session.config.stakes, currency/profile details, the balance and a session token. Select a stake from that returned list. Amounts use integer minor currency units; 100 EUR minor units means €1.00. Feature and bonus sessions have their own paid-stake schedules.
3. Submit one round
POST https://staticroit.dev/api/developer/platform/rounds
Content-Type: application/json
x-sr-api-key: YOUR_PRIVATE_DEVELOPER_KEY
Authorization: Bearer YOUR_LAUNCH_TOKEN
{"requestId":"YOUR_NEW_UUID","stakeMinor":100}Create a UUID for each new paid round. If a request times out, retry with that same UUID and stake. Do not generate a second UUID to recover an uncertain response. Only present the credited result once the returned state is settled. Preserve the round ID and recorded outcome; the client must not calculate or draw a replacement result.
4. Recover and inspect
Read GET /api/developer/platform/rounds/{roundId} or GET /api/developer/platform/rounds using the same key and Bearer token. Use POST /api/developer/platform/rounds/{roundId}/recover with an empty JSON body for an interrupted round. A replay reads the saved result and does not place a new bet.
Keep requests tied to their original account/session. Rate limits apply across all keys: 60 development requests/minute and 10,000/day. A 429 response requires backing off; an uncertain round still retains its original request ID.
Choose the right access
Developer keys start with sr_dev_ and authorize development tools. Commercial data keys start with sr_com_ and read the purchased onboarding package. They are not interchangeable. Signed operator wallet credentials and production game access require separate provisioning and acceptance.
The current RGS and games are development-only. A paid subscription or onboarding package does not provide real-money production distribution, certification or approved market access.