Kulku.io

Kulku.io is Thril's partner for access control. Unlike Thril's other access integrations, Kulku.io does not issue PIN codes or key fobs through Thril. Instead, customers get a door-opening button in the Thril app, and Thril decides when that button works — during a reservation, or during a membership's allowed access times.

Prerequisites

You need Kulku.io hardware configured at your venue. Kulkutech delivers your API address, building ID, customer identifier and encryption key directly to you; enter them into Thril yourself. For help, contact your Kulkutech contact person or Thril support.

To enable

1. Open Settings → System → Integrations → Kulku.io
2. Enter your API address, Building ID, Customer identifier and Encryption key
3. Configure the offset times and fallback instructions (see below)
4. Toggle Integration status to Active
5. Select Create integration (or Update integration) to save
6. List each resource's doors under the resource settings, and each membership's doors under the membership's integration settings
7. Optionally verify the setup with Test by opening a lock

Configuration options

• API address: the address Kulkutech gave you, for example https://yourvenue.kulku.io
• Building ID: the building identifier Kulkutech gave you
• Customer identifier: your customer identifier in Kulku.io
• Encryption key: used to sign every open request. Thril never sends the key itself to Kulku.io.
• Device identifier: optional, only fill this in if Kulkutech told you to
• Access offset times: how many minutes before and after a reservation the door-opening button works
• Fallback instructions: a message shown to customers if Thril detects an issue with Kulku.io (for example, "If the door doesn't open, please contact the venue staff."). Enable Always show fallback instructions to display it to all customers regardless of Kulku.io's status. You can also set resource-specific fallback instructions under each resource's settings.
• Doors (per resource and per membership): the lock names this resource or membership opens

Doors

Kulku.io has no way to list your locks, so door names are typed in by hand and must match the lock names configured in Kulku.io exactly — for example Etuovi. A resource or membership can have several doors; each one appears as its own button for the customer. The display name is what the customer sees, so it can differ from the lock name.

If a resource has no doors listed, its customers get no button at all.

Memberships

Members get the door-opening button during the allowed access times set on the membership's integration configuration. Outside those times the button is refused, as it is for members whose membership is paused, has unpaid periods, or is not yet (or no longer) active.

Troubleshooting

• Test by opening a lock verifies your API address, building ID, customer identifier and encryption key in one go. Note that it opens a real door. In Kulku.io's test environment the request succeeds but no door opens, because the test server does not talk to the hardware.
• "Cannot find lock by name" means the door name in Thril does not match the lock name in Kulku.io.
• "Access denied: wrong digest" means the encryption key, building ID or customer identifier is wrong.
• Inactivating the integration immediately removes the door-opening button from all reservations and memberships. Nothing needs cleaning up on Kulku.io's side, because Thril never provisions anything there.
• For help configuring your Kulku.io hardware or software outside of Thril, contact your Kulkutech contact person. For help with the integration in Thril, contact Thril support.