At a glance
- Status
- Needs an integration
- Lines
- Cloud-managed readers and door controllers
- Members can use
- Cards
- Needs
- A Kisi API key and a small integration between the two clouds
How it connects
- Member taps a card at the Kisi reader
- Kisi cloud
- Integration asks Chronix Hub
- On yes, integration calls Kisi's unlock API
With Kisi the lock is controlled from Kisi's cloud, so there is no box on your network to translate. An integration (a small cloud service your integrator runs) sits between the two: it learns of an attempt, calls the Chronix Hub verify endpoint, and only if the answer is granted: true does it call Kisi's unlock API.
Chronix Hub does not ship a Kisi integration today and is not an official Kisi partner. The integration is built against the open HTTPS API described on the Any HTTPS-capable device page. The studio side is ready now.
Supported hardware
Kisi manages the hardware. What matters is that your Kisi setup can expose each attempt to your integration.
- Kisi cloud-managed readers and door controllers.
- Confirm with your integrator which attempts Kisi will pass to the integration, and how fast, before you rely on it for a busy door.
What members can use
Cards are what we list for Kisi today.
Card
The card number the Kisi reader reads, added under the member's Door access tab and forwarded by the integration.
Other credentials
A QR pass or one-time PIN from the portal needs a device that can read it and send it to the integration. Ask your integrator before you promise it to members.
Set it up, step by step
The studio side takes minutes. The integration is for your integrator.
Create the door
Doors tab: name it, pick a schedule and anti-passback time.
Add the device
Devices tab, Add device. Choose vendor Kisi, pick the door, and add the integration's public IP to the allowlist.
Copy the key and device ID
The key is shown once. Give it and the device ID to your integrator through a password manager.
Create a Kisi API key
In Kisi, create an API key for the integration. The integrator now holds two keys: Kisi's and Chronix Hub's.
Build the integration
It asks the verify endpoint first and calls Kisi's unlock API only on granted: true. Any error, timeout or non-200 means no unlock.
Test
Tap a card and watch the Live Log. Freeze that member and tap again to confirm the refusal.
Two keys, two jobs
The Chronix Hub device key only lets the integration ask door-access questions. The Kisi API key only lets it unlock. Keep them in the integration's secret store and rotate either one independently: Regenerate key in Chronix Hub kills the old key instantly.
Troubleshooting
| What you see | Likely cause | Fix |
|---|---|---|
| Nothing in the Live Log | The integration never reached Chronix Hub. | Check the key, device ID, allowlist (the integration's public IP) and its internet. |
| Granted in the log but the door stays locked | The integration did not call Kisi's unlock API, or the Kisi key is invalid. | Check the integration logs and the Kisi API key. |
| unknown_credential on every tap | The card is not registered, or the number format differs. | Add the credential using the exact number the integration sends. |
| Slow to open | Two cloud calls in a row add network time. | Ask your integrator to place the integration close to both services. |
| 403 from the verify call | The integration's IP is not in the allowlist. | Add its public IP to the device's allowlist. |
What to ask your integrator
Ask before you commit.
- How does the integration learn about each attempt at the Kisi reader?
- Does it call the HTTPS verify endpoint first and unlock via Kisi only on granted: true?
- Will every error or timeout leave the door locked?
- Who hosts and maintains the integration, and what happens if it goes down?
- Where are the Kisi API key and the Chronix Hub device key stored?
Frequently asked questions
Is there a Kisi integration?
Not bundled. Kisi works through an integration built against the open Chronix Hub API. Chronix Hub is not a certified or official Kisi partner.
Does the door still work if Chronix Hub is unreachable?
That is a design choice for your integrator. The Chronix Hub server never says yes because of an error. Whether the door opens during an outage depends on the integration and your Kisi setup.
Can members use the QR or one-time PIN?
Only if your Kisi hardware can read them and the integration forwards them. Cards are the credential we list for Kisi today.
What is the quickest option for a single door?
A web kiosk works today with no integration.
Other ways to connect
Product names belong to their owners. Chronix Hub is not a certified or official partner of any hardware maker and does not sell hardware.
Want to see door access on your own studio?
Book a short demo and we will walk through your door, your hardware and your membership plans.