Sandbox Testing
Test your integration without hitting real data sources. The sandbox environment simulates all check workflows.
Getting started
Use a sandbox API key (prefixed gn_test_) to send requests to the same API base URL. Sandbox requests are free and do not appear on your invoice.
curl -X POST https://api.gonos.co/api/v1/candidates \
-H "X-API-Key: gn_test_your_key_here" \
-H "Content-Type: application/json" \
-d '{"first_name": "Jane", "last_name": "Doe", "email": "jane@example.com"}'Magic last names
Use these special last names to trigger specific check outcomes. Checks complete instantly in sandbox mode.
| Last Name | Result |
|---|---|
Testclear | Check completes with a clear disposition |
Testconsider | Check completes with a consider disposition |
Testreview | Check completes with a review disposition |
Testfail | Check fails with a processing error |
Testslow | Check stays in processing for 60 seconds |
Testdispute | Check completes, then a dispute is auto-filed |
Test scenarios
Happy path
- Create a candidate with last name
Testclear - Create a consent session and mark it complete
- Create a check — it completes immediately with disposition
clear - Fetch the report to verify the results
Adverse action flow
- Create a candidate with last name
Testconsider - Complete consent and create a check
- Initiate an adverse action on the completed check
- Wait the 5-business-day period (instant in sandbox)
- Finalize the adverse action
Dispute flow
- Create a candidate with last name
Testdispute - Complete consent, create a check, and wait for completion
- A dispute is auto-filed — test your dispute handling workflow
- Resolve the dispute to complete the flow
Webhook testing
- Register a webhook endpoint (use a service like
webhook.sitefor testing) - Create checks with different magic last names
- Verify that your endpoint receives the correct event types
- Test your signature verification with the webhook secret
Sandbox limitations
- Sandbox checks do not query real data sources (courts, OFAC, NSOPW, etc.)
- Consent sessions auto-complete — no email is sent to the candidate
- Adverse action waiting periods are bypassed
- Sandbox data is periodically purged (every 30 days)
- Rate limits are more lenient in sandbox (300 req/min vs 120 req/min)
Switching to production
When you are ready to go live, swap your API key from gn_test_ to gn_live_. No other code changes are needed — the API surface is identical.