KEYVOX API
★ Only Publicly Available OpenAPI DocumentIOTDevice ManagementapiKey7 EndpointsREST
For Agents
List smart-lock units and lockers, issue time-limited PIN access tied to bookings, trigger remote unlocks, and read recent lock events through 7 HMAC-signed KEYVOX endpoints.
Use for: I want to issue a smart-lock PIN for a guest's booking, Trigger an unlock on a KEYVOX smart lock for a verified guest, List every smart-lock unit at my property, Get the recent lock events for unit ABC123
Not supported: Does not handle reservation creation, payment processing, or property listing - use for KEYVOX smart-lock and smart-locker access control tied to existing bookings only.
Jentic publishes the only available OpenAPI specification for KEYVOX API, keeping it validated and agent-ready. The KEYVOX API is the integration surface for KEYVOX's smart-lock and smart-locker platform, used by accommodations, rental spaces, and coworking facilities to issue time-limited PIN access tied to a reservation. The seven endpoints split into Smart Lock operations (list units, create a one-time lock pin, unlock a unit, read recent lock events), Smart Locker operations (list lockers, create a locker pin), and Booking operations (read booking orders). Authentication is an HMAC signature passed in the Authorization header, and the base URL is https://eco.blockchainlock.io/api/eagle-pms.
Install Jentic One Beta
Connect the KEYVOX API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the KEYVOX 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fkeyvox.co%2Fkeyvox" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fkeyvox.co%2Fkeyvox" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 KEYVOX API.
List the smart-lock units registered to the authenticated property
Issue a time-limited lock PIN tied to a booking for guest access
Trigger a remote unlock on a specific KEYVOX smart lock
Read recent lock events for one or more units to audit access
List the smart lockers and issue locker PINs for parcel or item handover
Read the booking orders that drive access-grant decisions
Use Cases
Patterns agents use KEYVOX API for, with concrete tasks.
★ Self Check-In for Short Lets
Generate a time-limited lock PIN when a short-let booking is confirmed, valid only for the booking's check-in window, and send the PIN to the guest. The /v1/createLockPin endpoint accepts the booking parameters; /v1/getBookingOrders surfaces the booking that triggered the request. Pair the two with a messaging API and self check-in works end to end without a key handover.
POST /v1/createLockPin with the booking_id and check-in window to create a time-bounded PIN, then deliver the PIN to the guest
Coworking Space Locker Allocation
Allocate a smart locker to a coworking member or visitor by listing available lockers via /v1/getLockers and issuing a PIN with /v1/createLockerPin. The PIN is scoped to the locker and expires after use, so allocation is automatic and lockers free up cleanly. Most coworking platforms ship this in a couple of days.
GET /v1/getLockers to find a free locker, then POST /v1/createLockerPin with the chosen locker_id and the recipient details
Access Audit Across Properties
Audit who accessed which unit by polling /v1/locks/events for each unit on a schedule and writing the events to a downstream log store. Combined with the booking orders endpoint, the audit links each unlock to the booking that authorised it, which is critical for dispute resolution and security reviews.
POST /v1/locks/events with the unit IDs to fetch, then store the events alongside the matching record from /v1/getBookingOrders
AI Agent Stay Concierge
An AI agent that supports guests during a stay uses Jentic to call KEYVOX at the right moment - issuing a PIN ahead of arrival, triggering an emergency unlock if a verified guest is locked out, or reading recent events to confirm access worked. Jentic injects the HMAC signature per call so the agent never holds the signing key.
Through Jentic, search for 'create a keyvox lock pin', load POST /v1/createLockPin, and execute it with the guest's booking_id
Key Endpoints
7 endpoints — jentic publishes the only available openapi specification for keyvox api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/v1/getUnits
List smart-lock units
POST
/v1/createLockPin
Create a time-limited lock PIN
POST
/v1/unlock
Trigger a remote unlock
POST
/v1/locks/events
Read recent lock events
POST
/v1/getLockers
List smart lockers
POST
/v1/createLockerPin
Create a smart-locker PIN
POST
/v1/getBookingOrders
Read booking orders
POST
/v1/getUnits
List smart-lock units
POST
/v1/createLockPin
Create a time-limited lock PIN
POST
/v1/unlock
Trigger a remote unlock
POST
/v1/locks/events
Read recent lock events
POST
/v1/getLockers
List smart lockers
POST
/v1/createLockerPin
Create a smart-locker PIN
POST
/v1/getBookingOrders
Read booking orders
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the KEYVOX API by hand means computing its HMAC signature for every request, calling eco.blockchainlock.io/api/eagle-pms, and mapping lock, locker, and booking actions to their POST shapes yourself. Through Jentic you install once, import the KEYVOX API from the API Directory, store the signing key once, and your agent calls it.
Permission scoping
KEYVOX carries its targets in the POST request body rather than a resource id in the URL path, so limit the agent to the operations it needs, such as getUnits and getBookingOrders. You choose that set, so an action like unlock or createLockPin is not included unless you add it.
Credential isolation
Your KEYVOX HMAC signing key is stored once, encrypted, by your own Jentic One instance and injected at execution time. Jentic computes the signature per request, so the agent never holds the key or sees the signed payload.
Intent-based discovery
Agents search Jentic by intent such as 'create a KEYVOX lock pin' or 'unlock a KEYVOX lock', and Jentic returns the matching KEYVOX operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using KEYVOX API through Jentic.
Why is there no official OpenAPI spec for KEYVOX API?
KEYVOX does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call KEYVOX API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the KEYVOX API use?
An HMAC signature passed in the authorization header. The signing key is issued from the KEYVOX partner console and signs each request payload. Through Jentic, the signing key is held in the encrypted vault and the signature is computed per call so the raw key never enters the agent's context.
Can I issue a time-limited PIN with the KEYVOX API?
Yes. POST /v1/createLockPin with the unit identifier and the booking window returns a PIN that is valid only for that window. The same pattern applies to lockers via POST /v1/createLockerPin, where the PIN is scoped to the chosen locker.
What are the rate limits for the KEYVOX API?
The OpenAPI spec does not publish a rate limit. With seven endpoints and request volumes typically driven by booking events, throughput rarely hits a hard limit. If you receive HTTP 429, back off exponentially and retry the PIN-creation call.
How do I trigger a remote unlock through Jentic?
Search Jentic for 'unlock a keyvox lock' to find POST /v1/unlock, load its schema, and execute it with the unit identifier and booking context. The Jentic flow is pip install jentic, then client.search, client.load, and client.execute. Jentic injects the HMAC signature for you.
Can I read recent lock events with the KEYVOX API?
Yes. POST /v1/locks/events returns recent events for the supplied unit identifiers, which you can pair with /v1/getBookingOrders to link each unlock to the booking that authorised it. This is the data set used for access auditing.
GET STARTED