Sandbox and test data
Test keys return demo data only. Synthetic inputs that trigger every outcome: passed, review, failed, matches.
Any key that is not a live key runs in the sandbox. Sandbox responses are demo data with the same shape as live responses, plus "environment": "sandbox". No real register, list or document check is ever called, and sandbox calls do not use up your plan's checks.
Get a sandbox key#
Sign up, verify your email and create a key under API keys. New keys are test keys. You do not need a paid plan or a sales call.
Test data#
Use these inputs to get each outcome. Everything here is made up. Never send real people's data to the sandbox.
UK business checks
| companyNumber | Result |
|---|---|
00000000 | passed, risk low |
99999999 | review, risk medium |
| Any other number, or companyName only | passed |
Sanctions and PEP screening, and monitoring
| name contains | Result |
|---|---|
sanction test | A sanctions match |
pep test | A potential PEP match |
| Anything else | No match |
Identity checks
Any valid base64 string is accepted as an image in the sandbox, for example dGVzdA==. Set metadata.forceStatus to choose the result:
| metadata.forceStatus | Result |
|---|---|
| (not set) | passed |
review | review |
failed | failed |
curl -sS -X POST 'https://api.trustverify.co.uk/api/v1/kyc/verify' \
-H "Authorization: Bearer $TRUSTVERIFY_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"documentType": "passport",
"documentImage": "dGVzdA==",
"selfieImage": "dGVzdA==",
"metadata": {
"firstName": "Test",
"lastName": "Person",
"forceStatus": "review"
}
}'What the sandbox does not do#
- Webhook endpoints receive live events only. A test key can list endpoints but cannot create, change or delete them; use the dashboard or a live key.
- Sandbox checks are not stored as real decisions and do not appear in live reports.