Kiosk platform
Manage time capture units without bolting device control into your main app.
Account access
Sign in
Advanced connection
Guided setup
Finish setup
Connect your app
Generate the API key your ATS, payroll system, or custom app will use.
Custom scopes
Save this value now. It is only returned once.
Add a site
Create the client, site, or location the kiosk will belong to.
Set up a unit
Generate a QR that installs and binds the tablet to the selected site.
Advanced setup
Send a test clock event
Create a test person and send a clock in/out event through the API.
Units
Remote managementIntegration guide
v1Use tenant API keys for external software and device tokens for kiosk tablets.
http://localhost:8088
Authorization: Bearer ksk_live_...
Build the connection
Order of work- Create an account The customer signs up, creates a tenant, and receives an owner session plus the first root API key.
-
Create a site
Add one client/site record. Store the returned
client_idin the external system. - Create a scoped API key Use a restricted key for production integrations instead of sharing the root key.
-
Sync people
Upsert each worker/candidate with a stable
external_id, display name, optional PIN, and metadata. - Set up tablets Create setup tokens for Android face kiosks or PIN web kiosks. The response includes QR and APK links.
- Exchange clock events Post events from external systems or read events produced by kiosk tablets.
Scopes
Least privilegeCommon calls
ExamplesRules
Production useStable IDs: send the same external_id for the same person every time.
Idempotency: send Idempotency-Key on clock writes so retries do not create duplicate events.
Time format: send occurred_at as ISO 8601 UTC, for example 2026-09-14T09:00:00Z.
Setup tokens: setup QR responses include setup_url, qr_url, install_url, and agent_install_url.
Secret handling: raw API keys are only returned once. Store them in the external app secret store.