This release publishes the Lockii API reference.
The introduction is at help.lockii.app. It covers the base URL, how a request is authenticated, and which surface to use. The OpenAPI document is public at https://dash.lockii.app/api/v1/openapi.json, and it is generated from the same definitions as the handlers.
REST API — https://dash.lockii.app/api/v1. Create a key in Settings → Integrations → API and send it as x-api-key or Authorization: Bearer. The key is limited to that company.
User MCP — Claude, Cursor, ChatGPT, and VS Code can work in the account. Sign in with Lockii, or send an API key. The server is https://dash.lockii.app/api/mcp/user.
Customer MCP — Support tools such as Intercom Fin can read public inventory, build a checkout link, and look up a booking. The server is https://dash.lockii.app/api/mcp/customer.
Booking API — Public products, locations, availability, and checkout. No API key.
Login with Lockii — A person signs in with their Lockii account, and the integration calls the REST API or the User MCP as that user.
Lockii apps — Operators connect your product from Settings → Integrations and grant scoped offline access to their company.
Marketplace apps — List an operator's published inventory, check availability, price the hire with Lockii, and create the booking after you take payment. Signed webhooks keep listings and bookings in sync.
Bookings, customers, products, collections, blog posts, stock, locations, locks, trackers, pricing, maintenance, the inbox, and reports.
Timestamps are Unix milliseconds UTC. Amounts are integer cents. On a GET, each field is a query parameter. Other methods take a JSON body.
A key check is a location list. A 200 means the key works:
curl -H "x-api-key: <your-api-key>" \
https://dash.lockii.app/api/v1/location