KleverKey API

Name: KleverKey API
Brand: KleverKey API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIOTDevice ManagementapiKey15 EndpointsREST

For Agents

Provision smart locks, issue access invitations, manage smart cards and gateways, and audit door events on the KleverKey access platform.

Install Jentic One Beta

Connect the KleverKey API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the KleverKey API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with KleverKey API.

Provision an organization and its access groups on KleverKey

Issue an access invitation so a guest can unlock a specific door

GET STARTED

Start building with KleverKey API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for KleverKey API, keeping it validated and agent-ready. KleverKey is a smart lock and access management platform for offices, co-working spaces, and short-term rentals. The API exposes organizations, access groups, smart cards, gateways, locks, invitations, bookings, lock activation links, and the underlying event log, so an operator can provision a lock fleet, hand out access invitations, and audit who entered which door. It is well suited for property managers and co-working operators who need programmatic access control alongside their booking system.

Use Cases

Patterns agents use KleverKey API for, with concrete tasks.

★ Property Manager Access Control

Manage building access for a multi-tenant property without distributing keys. The /api/v1/organizations/{organizationId}/locks and /api/v1/organizations/{organizationId}/invitations endpoints let an operator add a lock, assign it to an access group, and invite a tenant in one workflow. Useful for serviced apartments, short-term rentals, and small property portfolios where tenants rotate frequently.

Create an invitation under organization 42 for guest email guest@example.com tied to lock id LK-001 valid until next Sunday.

Co-Working Booking Integration

Wire KleverKey into a co-working booking flow so a confirmed booking automatically unlocks the right door at the right time. The /api/v1/organizations/{organizationId}/bookings/{serviceName} endpoint creates a booking record bound to a lock and a window. Combined with the gateway and lock endpoints, an operator can run a fully automated unattended access flow for desks and meeting rooms.

Create a booking under organization 42 for service 'meeting-room-A' from 14:00 to 15:00 today for user member@example.com.

Access Audit and Event Reporting

Build a security audit feed by polling the KleverKey event log. The /api/v1/event-log endpoint returns lock unlocks, failed attempts, and gateway events that can be replayed into a SIEM, Slack channel, or compliance report. Best suited for facility managers who need a tamper-evident record of physical access for shared offices and regulated spaces.

Pull the KleverKey event log for the last 24 hours and post a summary of unlock events per lock to a Slack channel.

Smart Card Lifecycle Management

Manage the full lifecycle of physical smart cards in a KleverKey deployment. The /api/v1/organizations/{organizationId}/devices/smart-cards endpoint registers a card to a user and can revoke it later, so an HR or IT team can offboard departing staff without changing locks. Pairs naturally with HR systems that drive hiring and termination events.

Agent-Driven Facility Operations via Jentic

Let an AI agent answer facility questions like 'who entered the lab last night' or 'invite this contractor for tomorrow' by calling KleverKey through Jentic. The agent searches Jentic for the right access operation, loads the schema, and executes with the API key drawn from the Jentic vault. Far faster than wiring a custom KleverKey client into the operator's tooling.

Through Jentic, search for 'list KleverKey event log', load the /api/v1/event-log operation, and report failed unlock attempts in the last hour.

Key Endpoints

15 endpoints — jentic publishes the only available openapi specification for kleverkey api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/api/v1/event-log

Retrieve the access event log

GET

/api/v1/organizations

List organizations

GET

/api/v1/organizations/{organizationId}/locks

List locks for an organization

GET

/api/v1/organizations/{organizationId}/access-groups

List access groups

POST

/api/v1/organizations/{organizationId}/invitations

Send a guest access invitation

POST

/api/v1/organizations/{organizationId}/devices/smart-cards

POST

/api/v1/organizations/{organizationId}/bookings/{serviceName}

Create a booking that grants access

GET

/api/v1/event-log

Retrieve the access event log

GET

/api/v1/organizations

List organizations

GET

/api/v1/organizations/{organizationId}/locks

List locks for an organization

GET

/api/v1/organizations/{organizationId}/access-groups

List access groups

POST

/api/v1/organizations/{organizationId}/invitations

Send a guest access invitation

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

KleverKey API keys are stored encrypted in the Jentic vault. Agents call /api/v1/organizations and /api/v1/event-log through scoped Jentic tools without ever seeing the raw Authorization header value.

Intent-based discovery

Agents search by intent (e.g., 'invite a guest to a smart lock', 'audit door unlocks') and Jentic returns the matching KleverKey operation with its schema so the agent picks the right endpoint without reading the docs.

Time to first call

Direct KleverKey integration: 2-3 days to model organizations, locks, and event polling. Through Jentic: under 1 hour — search, load, execute.

FAQs

Specific to using KleverKey API through Jentic.

Why is there no official OpenAPI spec for KleverKey API?

KleverKey does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call KleverKey API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the KleverKey API use?

The KleverKey API uses an API key sent in the Authorization header on every request. Through Jentic, the API key is stored in the Jentic vault and injected into the request at execution time so the agent never holds the raw key.

Can I issue a guest invitation through the KleverKey API?

Yes. POST /api/v1/organizations/{organizationId}/invitations creates a time-bound invitation for a specific lock or access group. The recipient receives a link they can use to unlock the door during the configured window.

What are the rate limits for the KleverKey API?

KleverKey does not publish a public rate limit and the spec does not declare one. Treat per-organization endpoints as moderately throttled and avoid tight polling on /api/v1/event-log; use longer windows or webhooks where available.

How do I audit door unlocks through Jentic?

Search Jentic for 'KleverKey event log', load the GET /api/v1/event-log operation, and execute with a time range. Jentic injects the API key from the vault and returns the structured event entries for the agent to summarise.

Does the KleverKey API expose smart card management?

Yes. POST /api/v1/organizations/{organizationId}/devices/smart-cards registers a card for an organization and binds it to a user. This makes onboarding and offboarding employees programmatic instead of a manual desk operation.

KleverKey API

Connect the KleverKey API to your agent

Capabilities

Start building with KleverKey API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs