Test and live
What test does, and the one thing it cannot do.
A ehs_sk_test_ key runs against test. Same code path, same response shapes, same
validation.
What is identical
Registering roles and candidates, creating assessments, launch links, browser sessions, scheduling and webhooks all behave exactly as they do on live.
What is different
| Test | Live | |
|---|---|---|
| Credits | Separate monthly quota | Your credit balance |
| Recording | Off | On |
| Report | Never produced | Produced |
| Recruiter pipeline | Excluded | Candidates appear |
Recording is off because it is the largest cost per assessment. Scoring runs off that
recording, so a test assessment has nothing to score: it stays at processing, never
reaches completed, and GET /v1/assessments/{id}/report will not return one.
Build the create, launch, schedule and webhook flow against test. Use a live key for anything that has to read a finished report.
Test never reaches your recruiters
A test assessment does not appear on the pipeline board, in candidate search, or in any hiring surface. You can integrate against a customer's real organisation without putting anything in front of their team.
Quota
Test draws on a separate monthly allowance per assessment type, not on the credit pool.
GET /v1/usage reports the live balance; exhausting the test allowance returns
sandbox_quota_exceeded.
Next
- Assessments — create your first one
- Reference — rate limits, pagination, idempotency