A workflow that checks bookings, registers guests and generates temporary credentials that expire consistently with checkout.
The problem
Bookings and physical access lived in two separate systems. The PMS knew the guest, accommodation, check-in, checkout and booking status, while the access system handled the controller and automatic locks.
Without integration, someone had to retrieve and verify booking details, register the guest in the access system and manually create a credential valid for the stay.
The challenge was not merely generating a code; it was keeping bookings and physical access aligned without manual steps, reducing errors and ensuring credentials could not outlive the reservation.
The solution
BOOKING
↓
PMS API
↓
Booking retrieval and verification
↓
Guest registration
↓
Access system API
↓
Credential creation
↓
Physical access
↓
Expiry at checkout
The PMS becomes the source of truth for access duration: a credential inherits the booking window.
What I built
I designed the orchestration service to verify bookings, register the required data and request access credentials.
How it works
Booking > verification > guest registration > access API > temporary credentials > checkout expiry.
Engineering choices
API orchestration rather than duplicated systems. The PMS remains responsible for reservations, the controller for physical access, and the software acts as an orchestration layer between them.
Bookings are the source of truth. Credential validity is derived from booking check-in and checkout, not from independent time rules.
Outcome
A credential is not simply generated: it inherits its lifecycle from the booking.