
Integrating locks into an app, PMS or building platform happens through two distinct tool sets: cloud APIs for remote operations and Bluetooth SDKs for in-range phone control. Confusing them is the most common integration planning error.
When a third-party application needs to operate smart locks — a rental channel issuing codes, an office platform provisioning visitors or a hotel app delivering mobile keys — the lock vendor exposes programmable interfaces in two layers. The cloud API is typically a REST-style service over HTTPS: the application authenticates with OAuth-style credentials, creates passcodes or ekeys, sends remote unlock commands for online locks, queries lock state and receives webhook callbacks for unlock, low battery and tamper events. The mobile SDK is a library embedded in the integrator’s own iOS or Android app that handles Bluetooth discovery, secure connection, nearby unlock and offline credential logic without round-tripping to a server. Successful integrations use both layers deliberately, secure their credentials, and test rate limits and event delivery before launch. This guide maps the concepts and the vendor questions that matter. API and SDK availability, scopes and licensing for each platform are confirmed in writing per quotation.
| Cloud API | HTTPS services manage locks, credentials and events from a server; reach remote doors only when locks are online through Wi-Fi or a gateway. |
| Mobile SDK | Embedded iOS/Android libraries handle Bluetooth connection, nearby unlock and offline logic inside the integrator’s own app. |
| Authentication | OAuth-style client credentials, scoped tokens and signed webhooks separate professional platforms from open relay scripts. |
| Credentials by API | Common operations create dated passcodes, ekeys, cards and visitor links, with list, update and revocation endpoints. |
| Event delivery | Webhooks notify unlock, code use, low battery and door events; retry behavior and ordering guarantees must be documented. |
| Hardware dependency | Remote commands only execute on online locks through Wi-Fi or a gateway, so API design and hardware topology must be planned together. |
| Our policy | We provide interface documentation, sandbox or test devices and a technical contact; production credentials and limits come from the platform agreement. |
Server-side automation (rental channels, PMS, visitor management) builds on the cloud API; branded phone apps with nearby or offline control add the mobile SDK. Products needing both should design the credential model before writing code.
| Integration goal | Primary tool set | Key dependency |
|---|---|---|
| Issue dated rental codes | Cloud API from the booking backend | Locks support the target code type and sync path. |
| Branded tenant app | Mobile SDK plus cloud API | App team handles SDK release and store review. |
| Hotel mobile key delivery | Cloud API events from the PMS middleware | Credential service and gateway coverage at doors. |
| Visitor management kiosk | Cloud API for one-time credentials | Time zones and expiration semantics validated early. |
| Live remote concierge | Cloud API unlock plus webhook confirmation | Only online locks execute remote commands instantly. |
| Offline enterprise wallet | Mobile SDK with secured local credentials | Key storage and revocation rules on the device. |
APIs meet physical reality at the opening: gateways, metal doors and battery duty determine whether a clean API call reaches a lock in time. Pilot hardware and software together.
| Opening | Typical door | Lock approach |
|---|---|---|
| Rental unit door | Bluetooth lock with per-area gateway | Booking backend creates offline and online codes through the cloud API. |
| Office glass entrance | Online reader or controller | Visitor platform sends one-time credentials and receives entry webhooks. |
| Hotel guest room | RFID lock with mobile-key service | PMS middleware calls the key API; gateway pushes live updates. |
| Co-working door | Smart lock behind a glass facade | Member app embeds the SDK for nearby unlock even on weak Wi-Fi. |
| Logistics gate | Outdoor online lock | Remote commands require confirmed connectivity and fallback contacts. |
| Amenity room | Battery lock managed remotely | Webhook audits drive billing and abuse review in the operator app. |
APIs look similar in slides and differ in production. Before committing engineering time, integrators should collect the items below, all of which we help coordinate with the platform team.
| Component | Typical logic | Notes |
|---|---|---|
| API reference | Endpoints, scopes, versions and sandbox availability. | Engineering estimates depend on complete, current documentation. |
| SDK package | Supported OS versions, sample apps and release cadence. | Store approval and maintenance models must be understood. |
| Security model | Token types, secret rotation, webhook signing and IP options. | Protecting unlock endpoints is non-negotiable for production. |
| Limits and quotas | Rate limits, pagination, batch operations and retry rules. | Fleet launches can otherwise fail at peak check-in hours. |
| Event catalog | Event types, payloads, ordering and redelivery guarantees. | Audit and notification features depend on reliable events. |
An API is a server-to-server interface: your backend calls the lock platform over HTTPS to create codes, send unlock commands to online locks, query status and receive webhook events, and it works regardless of phone proximity. A mobile SDK is a software library built into your own iOS or Android app that talks to locks directly over Bluetooth, enabling nearby unlock, setup and offline credential storage when no server is reachable. Rental backends and PMS integrations mainly need the cloud API; branded tenant apps usually need the SDK plus selected API calls. Trying to do everything through the API — for example unlocking a Bluetooth-only lock from across the world with no gateway — simply will not work, so the hardware topology and interface choice must be designed together. Available interfaces per platform are confirmed in writing per quotation.
Yes, that is a standard integration pattern: when a reservation is confirmed, your backend or middleware calls the lock platform API with room or unit, arrival and departure, and receives a passcode or ekey that is delivered to the guest through your own message or email template. Webhooks then confirm usage and flag events such as early check-in attempts or low batteries. Requirements to nail down are time-zone handling for date windows, which code type works offline on the selected locks, gateway coverage for live revocation, idempotent retries when messages are resent and how cancellations and date changes update the credential. We provide test locks and support the integration workshops; endpoint details, rate limits and licensing for each platform are confirmed in writing per quotation.
Remote unlock is safe when the platform is built like any authenticated financial API: OAuth-style tokens with limited scopes, server-side secret storage, per-staff permissions, command confirmation via webhook, audit logs and optional two-factor approval for sensitive doors. It becomes dangerous when integrators embed long-lived secrets in phone apps, expose open relay endpoints or log unlock URLs. Physical safeguards matter too: remote commands only reach online locks, and high-security doors often disable remote unlock entirely or require dual approval. During due diligence, ask for the security whitepaper, token rotation procedure and webhook signing scheme rather than accepting a “REST API available” claim. We coordinate these reviews with the platform team and can propose architectures where remote unlock is restricted to reception roles.
Webhooks are the standard event channel — unlock records, code entries, low battery, tamper alerts and door-sensor changes — but delivery semantics vary by platform. Professional platforms sign payloads, retry failed deliveries with backoff and provide an API to reconcile or poll missed events, which matters because networks briefly fail and duplicate delivery is normal; consumers must therefore treat event IDs as idempotent. Ordering guarantees are weaker: two events generated seconds apart can occasionally arrive reversed, so audit logic should timestamp from the lock event time rather than arrival time. During the pilot, simulate an offline receiver and verify replay behavior. The event catalog, retry policy and reconciliation endpoints for the ordered platform are documented in writing before development starts.
API access is granted by the lock platform under its own developer and commercial terms, typically to the account owner: the brand or operator that owns the cloud project, not automatically to every buyer of a lock. The factory can help enable the service, supply documentation and coordinate technical onboarding, but it cannot assign rights beyond the platform agreement. Some platforms distinguish app-only users, business accounts with dashboards and certified developer partners with full API access, and a few advanced endpoints require an approved integration review. Buyers planning deep integrations should therefore confirm developer eligibility, fees, data-processing terms and supported regions before selecting hardware, because a great lock with no API entitlement cannot power the planned product. Current developer programs and licensing per platform are confirmed per RFQ.
Share your integration use cases, team stack and launch timeline with your RFQ. We coordinate API documentation, SDK packages, test devices and platform agreements, and support a joint pilot covering offline, retries and fleet-scale events.
Request Spec Sheet + QuoteTechnology overviewLast updated: October 31, 2026 · Reviewed by the Smart Lock Factory editorial team