Sandbox (test environment)
kinmu_sk_test_ keys never operate against real data: their tenant is a sandbox company with synthetic data (demo employees, sample check-ins and absences) that is auto-provisioned when the addon is enabled. Use it to build and test your integration.
- Resettable from the dashboard (my.kinmu.app → Developers).
- Lower limits than production: 30 req/min and 5,000 req/month (see rate limits).
If a test key is used without a provisioned sandbox, the API responds 401 (fail-closed) — it never falls back to real data.
Use test keys for development and for your CI pipelines; reserve live keys for production. Everything else (endpoints, scopes, shapes) is identical between sandbox and production.
Lifecycle
The sandbox is tied to the Public API addon: it is provisioned when the addon is enabled and deprovisioned when it is disabled. Disabling the addon is not a pause, it is a deletion.
When you disable it:
- All of the company’s API keys are revoked —
liveandtest— with reasonaddon_disabled. Re-enabling the addon does not bring them back: you have to issue new keys and redeploy your integrations. - All generated reports are deleted and their download URLs stop resolving. Download anything you need to keep beforehand.
- The sandbox company is deleted with all its data (demo employees, check-ins, absences and whatever you created yourself). Re-enabling the addon provisions an empty one with fresh synthetic data: the previous IDs no longer exist.
Disabling the addon takes production and sandbox out of service at the same time, and as far as data goes it is irreversible. Don’t use it as a maintenance switch: to cut off one integration, revoke its key.
A sandbox reset from the dashboard is a different thing: it wipes and regenerates the test data, but leaves your API keys alone.