We built PassLane with one conviction: access infrastructure should be invisible. Your guests shouldn't need to download another app. Your developers shouldn't need to understand lock firmware. And your operations team shouldn't need to manually encode a single keycard ever again.
That's why PassLane is API-first. We don't build guest apps — we give you the tools to embed world-class access directly into the app your guests already use.
Why an API-First Access Layer Matters
Most access control vendors sell closed ecosystems. You buy their lock, use their app, live on their roadmap. PassLane takes the opposite approach:
- Own the experience: Your guests stay inside your branded app. No redirects, no deep links, no "powered by" screens.
- Ship faster: Our SDK handles BLE communication, credential storage, and secure handshakes. You focus on your UI.
- Stay flexible: PassLane works with 20+ lock brands. Swap hardware without rewriting a line of code.
Getting Started with the PassLane SDK
The SDK is the fastest path to mobile keys in your app. Native libraries for iOS and Android, designed to drop in cleanly.
What you get:
- Lightweight footprint: Under 2MB. No bloat, no hidden dependencies.
- Full UI control: The SDK handles the cryptography and communication. You design the unlock experience — button, animation, haptics, whatever fits your brand.
- Secure by default: Credentials are stored in the device's secure enclave. Keys are time-bound, device-bound, and rotate automatically.
The PassLane REST API
For back-end integrations and fleet management, the REST API covers everything:
Provision and manage:
- Users and guests: Create access programmatically the moment a reservation hits your PMS. Revoke it on checkout. No manual steps.
- Spaces and devices: Query lock status, battery levels, and connectivity across your entire portfolio from a single endpoint.
- Access groups: Define permission sets like "All Common Areas", "Floor 3 Staff", or "Gym + Pool" and assign them in one call.
Automate:
- Webhooks fire on every meaningful event — door unlocked, credential issued, battery low, device offline. Pipe them into your ops dashboard, Slack, or monitoring stack.
Example: Mobile Key in a Hotel Loyalty App
Here's how a typical integration works end-to-end:
- Reservation confirmed: Your PMS sends the booking to your back-end.
- Access provisioned: Your server makes one API call to PassLane — guest gets access to their room and all linked common areas for exactly the duration of their stay.
- Key delivered: The PassLane SDK, embedded in your app, securely receives the credential. No push notification needed — it's ready when the guest opens the app.
- Door unlocked: Guest taps your custom unlock button. BLE handshake completes in under a second. Done.
The entire flow is automated. No front desk interaction. No keycard encoder. No app download.
What Makes PassLane Different
We're not a lock company that bolted on an API. We're an infrastructure company that spent a decade learning how locks work — processing over 100 million mobile opens across 38 countries — so you don't have to.
PassLane is lock-agnostic, PMS-agnostic, and works with any booking source: your PMS, an OTA, a direct booking engine, or even an AI agent. One API handles identity, timing, and access rules across all of them.
Ready to integrate?
Email dev@passlane.com to request API credentials and access to our developer sandbox. Most teams ship a working integration in under a week.
