Sandbox and test data
How the staging sandbox behaves and which test data it accepts.
The sandbox is the sk_test_… environment on https://api-staging.sekyro.ai. It runs
the same flow as production, never calls a government system with a real person's
data, and never bills a check.
Test data only
Never put a real person's national number, document or face into the sandbox. Use the test records below, or test personas you seed yourself.
National registry (population_registry)
The sandbox registry answers only for test records:
- the built-in test NNI, which passes. Your Sekyro AI contact shares it at onboarding; it is deliberately not printed in public documentation;
- the test NNIs you seed in the dashboard (sandbox environment → Settings → Test NNIs);
- any other valid NNI answers
nni_not_found.
Creating a sandbox session prefilled with an NNI you have not seeded answers
400 sandbox_nni_not_seeded. Details: Quickstart, sandbox test NNIs.
National eID (eid_auth)
Staging only
The sandbox uses a test provider instead of Houwiyeti:
| Input | Result |
|---|---|
Code 000000 | Passes |
Code 111111 | Expired code |
| Any other code | Wrong code |
NNI 1000000161 | No Houwiyeti app (eid_not_enrolled) |
NNI 1000000258 | Provider outage (eid_unavailable) |
| Any other valid NNI | Receives a code |
The sandbox identity returned by the test provider is a synthetic test person.
Keys, attestation and billing
- Sandbox keys start with
sk_test_and are minted from your app's page in the dashboard (API keys → Mint key). - Turnstile and native app attestation are never enforced in the sandbox.
- Sandbox checks are always free (pricing).