Appearance
Staging Environment
Every operator gets a separate staging tenant for testing. The staging environment mirrors the full production API surface with resettable data, allowing safe end-to-end testing.
How It Works
FAST uses separate tenants for staging and production. When you onboard, you receive a staging tenant with its own API key. When ready to go live, a production tenant is created (via "Clone to Production") with your rulesets and challenge tiers, no player data, and new keys.
- Staging tenant: Full API access, data can be reset at any time
- Production tenant: Full API access, data reset is blocked
Both use the same X-API-Key header:
X-API-Key: your-api-keyReset Staging Data
Reset All Data
bash
curl -X POST https://api.fundedfast.eu/v1/sandbox/reset \
-H "X-API-Key: YOUR_STAGING_API_KEY"Clears all challenges, funded accounts, bet events, and webhook deliveries for the staging tenant. Only works on tenants with environment = staging.
Reset Per-User Data
bash
curl -X POST https://api.fundedfast.eu/v1/sandbox/reset/user-001 \
-H "X-API-Key: YOUR_STAGING_API_KEY"Removes all data for a specific user while preserving other test users. Useful when rerunning a single test scenario.
WARNING
Reset is blocked on production tenants. If you need to clean up production data, contact FAST support.
Recommended Test Flow
- Reset staging data.
bash
curl -X POST https://api.fundedfast.eu/v1/sandbox/reset \
-H "X-API-Key: YOUR_STAGING_API_KEY"- Purchase a challenge.
bash
curl -X POST https://api.fundedfast.eu/v1/challenges/purchase \
-H "X-API-Key: YOUR_STAGING_API_KEY" \
-H "Content-Type: application/json" \
-d '{"userId": "test-user-1", "challengeTierId": "TIER_ID"}'- Validate a bet (dry run).
bash
curl -X POST https://api.fundedfast.eu/v1/bets/validate \
-H "X-API-Key: YOUR_STAGING_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"userId": "test-user-1",
"externalBetId": "test-bet-1",
"stakeAmount": 5,
"odds": 2.0,
"betTypeIdentifier": "single",
"status": "placed"
}'- Place and settle bets to drive the challenge toward target.
bash
curl -X POST https://api.fundedfast.eu/v1/bets \
-H "X-API-Key: YOUR_STAGING_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"userId": "test-user-1",
"externalBetId": "test-bet-1",
"stakeAmount": 5,
"odds": 2.0,
"betTypeIdentifier": "single",
"status": "settled-won",
"settlementAmount": 10
}'- Check user progress.
bash
curl -H "X-API-Key: YOUR_STAGING_API_KEY" \
https://api.fundedfast.eu/v1/users/test-user-1/progress- Verify webhooks are arriving at your endpoint.
Going to Production
When integration testing is complete:
- Request production promotion from the FAST admin panel (Clone to Production)
- You receive a new production API key and widget key
- Update your backend
.envwith the production key - Production tenant starts with zero data - no test data leaks
Key Differences
| Staging | Production | |
|---|---|---|
| Data reset | Allowed (/sandbox/reset) | Blocked |
| API surface | Identical | Identical |
| Webhooks | Delivered normally | Delivered normally |
| Rate limits | Same as production | Same as production |
| Analytics | Excluded from platform stats | Included |