Skip to content

💡 Door Access PIN Management

Self-service PIN code management for door access providers

The Idea

Door access providers can autonomously manage PIN codes for guest reservations without requiring custom integration work. Set, update and synchronize PINs through the LIKE MAGIC API—guests receive access codes instantly in their guest journey app.

How It Works

The Flow:

  1. Door provider calls the API to set a PIN for a reservation
  2. LIKE MAGIC validates the reservation and assigned unit
  3. PIN is stored at the unit level (room-based, not reservation-based)
  4. Guest app displays the updated PIN immediately
  5. All guests in the same unit see the same PIN (matches physical door behavior)
sequenceDiagram
    participant Door Provider
    participant "LIKE MAGIC"
    participant Guest App

    Door Provider->>"LIKE MAGIC": 1: Set PIN for reservation
    activate "LIKE MAGIC"
    "LIKE MAGIC"->>"LIKE MAGIC": 2: Validate reservation & unit
    "LIKE MAGIC"->>"LIKE MAGIC": 3: Update PIN in unit configuration
    "LIKE MAGIC"->>"LIKE MAGIC": 4: Update accessible doors on reservation
    "LIKE MAGIC"-->>Door Provider: 5: Success response
    deactivate "LIKE MAGIC"

    Guest App->>"LIKE MAGIC": 6: Fetch reservation details
    "LIKE MAGIC"-->>Guest App: 7: Returns updated PIN

What You Get

Real-time PIN management that works like physical door systems:

  • Autonomous PIN updates without LIKE MAGIC team involvement
  • Instant synchronization to guest journey apps
  • Unit-level storage matching physical lock behavior
  • Support for concurrent reservations with shared access
  • Self-service integration for door providers

Perfect For

  • Door access provider developers building integrations
  • Property operations teams managing access systems
  • Integration partners creating door access solutions
  • Technical teams implementing OfflinePIN systems

Technical Details

Supported Door Providers

This API is only supported for the OfflinePIN door provider. Properties using other door access systems (Salto, ASSA ABLOY, etc.) cannot use this endpoint.

Reservation Requirements

Before updating a PIN, ensure: - Reservation status is CONFIRMED or IN_HOUSE - A unit is assigned to the reservation - The property uses the OfflinePIN door provider

Unit-Level PIN Behavior

Important: PINs are stored at the unit level, not the reservation level.

Scenario Behavior
Single reservation for unit PIN applies to that reservation
Multiple reservations for same unit All reservations receive the same PIN
New reservation assigned to unit Inherits the current PIN configuration

Example: A unit with two concurrent reservations (one IN_HOUSE, one CONFIRMED) will share the same PIN. Updating via either reservation ID changes the PIN for both guests.

This behavior aligns with physical door access systems where PINs are tied to locks, not individual stays.

Key APIs

Ready to build? Check out the Inventory API - Door Access section in Swagger UI for complete API documentation.