Home · Integrations · RemoteLock
Door access · Partner integration
RemoteLock + Birdie: 24/7 Golf Simulator Door Access
Birdie is booking and venue-management software for indoor golf simulator businesses, and RemoteLock is one of five smart-lock providers we integrate for automated door access. A customer books a bay, receives a link, clicks it, and the door unlocks — the same experience across every provider we support. Members and one-time guests both use the identical flow, with no app to install and no code for staff to hand out.
Customer Experience
Here is exactly what an end customer sees, start to finish:
- Books a bay on their venue's Birdie site.
- Receives a confirmation with a one-tap unlock link (email, and optionally SMS).
- At their session time, clicks the link — RemoteLock issues a time-bounded PIN or mobile credential.
- Enters the venue.
- Access expires automatically at session end.
No app install required. No fob. No schedule to configure.
Technical Implementation
Each of RemoteLock's seven required certification items, with the specific implementation detail.
1. API Gateway
All traffic routes through RemoteLock's documented Connect API at connect.remotelock.com/api/v2 via a single shared client wrapper. Every request — token exchange, device discovery, access-person and credential management — passes through that one wrapper. There are no direct-server calls and no deprecated endpoints.
2. OAuth 2.0 Authorization Code Grant
We implement the full authorization-code flow with an HMAC-signed state parameter (nonced, 10-minute expiry) for CSRF protection, and request the explicit minimum-necessary scopes. Token exchange is form-urlencoded per RFC 6749. Refresh tokens auto-rotate when fewer than 30 minutes remain, so a venue connection never lapses mid-session.
3. Device Discovery & Mapping
On connect, Birdie fetches the venue's device list — name, type, ID, and online status — and persists it to our canonical door-mapping table. Operators assign each device a friendly name and map it to a specific bay from their Birdie dashboard. A re-sync reconciles added and removed devices and flags orphaned mappings so nothing silently breaks.
4. Access Person Creation & PIN Retrieval
Each customer becomes a RemoteLock access person on their first booking, and that identity is cached against their Birdie customer record for reuse on later visits. Credentials are issued per booking as a PIN or a mobile (BLE) credential, returned to Birdie, and delivered to the customer through their unlock link. There is no shared code and no manual hand-off.
5. Access Assignment to Devices
Credentials are scoped at issue time to the specific device backing the customer's booked bay. A customer holding a lesson-bay booking cannot unlock a simulator bay they did not book. Access is granted to exactly the door required — nothing wider.
6. Reservation Change Handling
Cancellations revoke the credential immediately. Reschedules and extensions re-window the credential — revoking and reissuing if the provider dropped the credential in the interim. Membership and plan changes recompute door eligibility. A prebuild CI guard fails our deploy if any new booking-mutation code path skips this revoke/reissue fan-out, so the door state can never drift from the reservation state.
7. Support Documentation
This page is the public reference. Inside every Birdie venue account there is also an in-product setup guide at Settings → Door Access → RemoteLock that walks an operator through connecting their account, mapping devices, and testing a live unlock.
Optional Functionality
Which optional RemoteLock items we support, and which we intentionally don't.
| Optional Feature | Status | Notes |
|---|---|---|
| Webhooks for access events | Roadmap | Owner-facing access log is on the roadmap when operators request it. |
| Door groups | Not offered | Our multi-door fan-out at the booking level achieves the same outcome. |
| readyPIN (offline devices) | Not offered | Our model requires online devices for real-time unlock. |
| BLE mobile credentials | Supported | Delivered via the same unlock link — no separate app install required. |
| Card numbers | Not offered | Our UX is link-based, not fob-based. |
| Retroactive guest backfill | Not offered | We sync forward-only from the integration connect date. |
| First-class access schedules | Not offered | Per-booking, time-bounded credentials give equivalent control. |
For Venue Owners
If you run a venue and want to enable RemoteLock at your location, log into your Birdie dashboard and go to Settings → Door Access, where you can connect Avigilon Alta, RemoteLock, Kisi, PDK, or UniFi Access. Map each device to a bay and Birdie handles credential issuance, delivery, and expiry on every booking from that point on.
RemoteLock door access — FAQ
Does Birdie integrate with RemoteLock?
Yes. Birdie grants time-limited access via RemoteLock: a PIN or mobile credential is auto-issued at booking time, delivered by SMS or email, and expires when the session ends.
How do customers receive their RemoteLock code?
Birdie sends the PIN or mobile credential automatically by SMS or email when the booking is made, so there is nothing for staff to hand out.
For RemoteLock Partners & Certification Reviewers
For certification questions, integration technical questions, or partnership inquiries, email luke@birdiegrow.com. Birdie is a live production platform with active venues running on Avigilon Alta, PDK, UniFi Access, and Kisi, and we are onboarding our first RemoteLock production venue this month.