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.

PrerequisitesCopy Anchor Link

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 enableCopy Anchor Link

1. Open Settings → System → Integrations → Kulku.io
2. Enter your API address, Building ID, Customer identifier and Encryption key
3. Set the access times and fallback instructions (see below)
4. Set Status to Active
5. Select Save changes
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 under Actions → Test by opening a lock

Configuration optionsCopy Anchor Link

• 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 before the reservation and Access after the reservation: how many minutes before the reservation starts and after it ends the door-opening button works
• Maximum distance from the venue: customers must be within this distance for the door-opening button to work. A weak phone signal can stop a customer from opening the door, and they contact you instead. Your staff can open a door wherever they are. Set the venue's address coordinates first.
• 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

DoorsCopy Anchor Link

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.

MembershipsCopy Anchor Link

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.

Updating existing reservationsCopy Anchor Link

After enabling the integration, select Actions → Update future reservations to add the door-opening button to upcoming reservations. This is helpful when you first connect the integration or add doors to a resource. The action is available once the integration is active.

Delete the integrationCopy Anchor Link

Select Delete integration to remove the Kulku.io settings from your venue. Thril also removes the Kulku.io settings of each resource and each membership. You can set up the integration again later.

You can't delete the integration while upcoming reservations have the door-opening button or memberships give access through Kulku.io. Remove the integration from those memberships, and delete the integration once the reservations have ended. Set Status to Inactive in the meantime, and the door-opening button stops opening doors.

TroubleshootingCopy Anchor Link

• Actions → 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.