Testing
Sandbox credentials work against the sandbox API, whose base URL is in the Operator Portal under Credentials, and a sandbox catalogue with real provider games.
- Money is test money. Fund your test players generously: provider test suites drain balances.
- Admit the address we call your wallet from if it sits behind an allow-list. It is listed in the Operator Portal under Credentials.
- Test the unhappy paths: a bet over the balance, a repeated
transaction_id, a rollback for an id you never saw, a slow wallet. - Use the tools: the Postman collection and the signature tester.
Scenario values
In the sandbox these values in an ordinary signed call answer with a refusal, exactly as production would, so every error branch of your integration can be built and tested on demand. In production they are ordinary values.
| Value | Where | Answer |
|---|---|---|
sandbox_player_blocked | player_id of POST /v1/sessions | 409 PLAYER_BLOCKED |
ZZ | player_country of a session or a demo | 409 GAME_RESTRICTED_IN_COUNTRY |
sandbox_game_unavailable | game_id of a session, the demo {id}, any of game_ids | 409 GAME_UNAVAILABLE |
sandbox_game_no_demo | {id} of POST /v1/games/{id}/demo | 409 NO_DEMO |
sandbox_player_free_spins_refused | player_id of POST /v1/free-spins | 409 FREE_SPINS_REFUSED |
sandbox_player_bonus_refused | one of player_ids of POST /v1/bonus-campaigns | 409 BONUS_CAMPAIGN_REFUSED |
sandbox_upstream_unavailable | player_id or game_id of a session, a demo, free spins or a bonus campaign | 503 UPSTREAM_UNAVAILABLE, retryable |
Refusals of your own wallet, such as INSUFFICIENT_FUNDS or a timeout, are yours to produce: the wallet test suite checks how your wallet answers them.