Sandbox access
A key, the SDKs, and documents that fail on purpose.
Most verification sandboxes only show you the happy path, which is the one case nobody needs to see. Ours ships test documents that produce all three verdicts, so you can build the review queue and the refusal copy before you have a live player.
- 3verdicts you can reproduce
- 1 working dayto issue a key
- 0obligation
Request a key
What we need to scope it
The key is scoped to markets and a region, so those two answers are the ones that matter. Everything else is optional.
- Test documents for every market you select, including ones designed to fail
- The API reference, the three client SDKs and a Postman collection
- A sandbox webhook endpoint you can point at your own staging
The key does not expire on a trial clock. It stops being useful when you go live, and not before.
About the sandbox
What you can and cannot do with it
Does it hit the real registers?
No. A sandbox that queried a national self-exclusion register would be putting test traffic into a live compliance system, which no operator of one permits. Register lookups return deterministic fixtures keyed to the test documents, so you can reproduce a hit on demand.
Are the test documents real?
They are synthetic specimens built to the real series formats. They exercise the parser, the authenticity checks and the failure paths without containing a real person's data.
How long does the key last?
Until you stop using it. There is no trial countdown, because a countdown converts an evaluation into a scramble and tells you nothing useful about the product.
Can we load-test it?
Within reason, and tell us first so we do not read it as an incident. The rate limits are documented and the sandbox is deliberately slower than production.