Duve has integrated with RemoteLock, using the DuveConnect outgoing webhooks API, to automate and enhance access code management for properties utilizing smart locks. This integration streamlines room access for guests by syncing Duve reservations with RemoteLock, generating PIN codes for each reservation. With real-time updates, hosts can manage access codes seamlessly, providing a fully automated and efficient guest check-in and check-out experience.
Overview
By integrating with RemoteLock through DuveConnect, Duve automates this process using outgoing webhooks that correspond to key reservation events. This ensures that access codes are securely generated and delivered to guests, improving operational efficiency and enhancing the guest experience. The integration extends Duve’s capacity to handle smart locks via real-time data transfer to RemoteLock, enabling a smooth and secure room access process.
Duve will send all the events to RemoteLock, and RemoteLock will send the access code to the guest's reservation.
Pricing:
The integration is a paid feature for 2 eur per unit/month. Reach out to your Customer Success Manager or to Duve's Support Team to request to enable RemoteLock integration.
How to Set Up the DuveConnect-RemoteLock Integration
Setup Steps in RemoteLock
In your RemoteLock Account, use the Authorize button in the Remotelock developer portal's App detail page to provide access to the Duve system.
Important: Rename the Remote Connect lock name to the same as the room number
Add the connected lock name in the details page in the Remote lock dashboard, to map the lock with the room.
Once the Authorization is completed, RemoteLock will provide the Client ID and Client Secret. Please save
Setup Steps in Duve
-
Setup Connection
- Go to Settings > Duve Connect > Add Incoming connection.
Click Create.
Show the Access Token and Copy (to add in later setup as the incoming_token!)
Show the Access Token and Copy (to add in later setup as the incoming_token!)
Add the Primary Code under Access Scopes:
Outgoing Webhooks
Each outgoing webhook corresponds to a specific reservation event. Below is a structured list of webhooks, their triggers, and the data payload format.
Navigate to Settings > Connections > DuveConnect.
Set Up Webhooks: Click on "Create New Connection" to add RemoteLock as an integration.
- Pre Check-In Done
- Pre Check-Out Done
- New Reservation Created
- Room Changed
- Reservation Status Changed
- ETA and ETD Updates
1. Pre Check-In Done
Description:
This webhook triggers when the pre check-in process for a guest is completed. It includes details of the guest’s estimated check-in time, identification, and other reservation-related data.
Endpoint:
Event Type:
preCheckInDone
Payload Format:
{
"accountId": "string",
"event": "preCheckInDone",
"resource": {
"id": "string",
"estimatedCheckInTime": "string",
"verifiedFirstName": "string",
"verifiedLastName": "string",
"passportUploaded": "boolean",
"guestsInfo": [
{
"firstName": "string",
"lastName": "string",
"email": "string",
"phone": "string",
"isPrimary": "boolean"
}
],
"externalId": "string",
"company": "string",
"externalPropertyId": "string",
"startDate": "string",
"endDate": "string",
"estimatedCheckInDateTime": "string"
}
}
2. Pre Check-Out Done
Description:
This webhook triggers when a guest completes the pre check-out process, containing information such as the estimated check-out time and guest details.
Endpoint:
Event Type:
preCheckOutDone
Payload Format:
{
"accountId": "string",
"event": "preCheckOutDone",
"resource": {
"id": "string",
"estimatedCheckOutDateTime": "string",
"verifiedFirstName": "string",
"verifiedLastName": "string",
"guestsInfo": [],
"externalId": "string",
"company": "string",
"estimatedCheckOutTime": "string"
}
}
3. New Reservation Created
Description:
This webhook triggers when a new reservation is created. It provides essential reservation details, including check-in and check-out times, start and end dates, and apartment number.
Endpoint:
Headers:
client_id
client_secret
incoming_token -
Find Access Token in Incoming Connection: 
Event Type:
reservationRoomAssign
Payload Format:
{
"accountId": "string",
"event": "reservationRoomAssign",
"resource": {
"id": "string",
"externalId": "string",
"startDate": "string",
"endDate": "string",
"apartmentNumber": "string",
"company": "string",
"externalPropertyId": "string",
"estimatedCheckInTime": "string",
"estimatedCheckOutTime": "string"
}
}
4. Room Changed on Reservation
Description:
This webhook triggers when a reservation is updated with a room change. It sends data on the updated apartment number and associated reservation details.
Endpoint:
Event Type:
reservationRoomAssign
Payload Format:
{
"accountId": "string",
"event": "reservationRoomAssign",
"resource": {
"id": "string",
"externalId": "string",
"startDate": "string",
"endDate": "string",
"apartmentNumber": "string",
"company": "string",
"externalPropertyId": "string",
"estimatedCheckInTime": "string",
"estimatedCheckOutTime": "string"
}
}
5. Reservation Status Changed
Description:
This webhook triggers whenever there is a status update on a reservation (e.g., from "Checked In" to "Checked Out"). It includes reservation timing and status data.
Endpoint:
Event Type:
updateReservationStatus
Payload Format:
{
"accountId": "string",
"event": "updateReservationStatus",
"resource": {
"id": "string",
"externalId": "string",
"bookingStatus": "string",
"externalPropertyId": "string",
"estimatedCheckInTime": "string",
"estimatedCheckOutTime": "string",
"startDate": "string",
"endDate": "string"
}
}
6. ETA Updated
Description:
This webhook triggers when the estimated time of arrival (ETA) is updated for a reservation. It contains updated check-in and check-out times.
Endpoint:
Event Type:
reservationDetailsUpdated
Payload Format:
{
"accountId": "string",
"event": "reservationDetailsUpdated",
"resource": {
"id": "string",
"externalId": "string",
"startDate": "string",
"endDate": "string",
"apartmentNumber": "string",
"estimatedCheckInTime": "string",
"estimatedCheckOutTime": "string"
}
}
7. ETD Updated
Description:
This webhook triggers when the estimated time of departure (ETD) for a reservation is updated. It includes updated check-out time and reservation period.
Endpoint:
Event Type:
reservationDetailsUpdated
Payload Format:
{
"accountId": "string",
"event": "reservationDetailsUpdated",
"resource": {
"id": "string",
"externalId": "string",
"startDate": "string",
"endDate": "string",
"estimatedCheckInTime": "string",
"estimatedCheckOutTime": "string"
}
}
8. Stay Dates Updated
Description:
This webhook triggers when the stay dates (start and end dates) are updated for a reservation. It provides the revised start and end dates along with other reservation details.
Endpoint:
Event Type:
reservationDetailsUpdated
Payload Format:
{
"accountId": "string",
"event": "reservationDetailsUpdated",
"resource": {
"id": "string",
"externalId": "string",
"startDate": "string",
"endDate": "string",
"apartmentNumber": "string",
"estimatedCheckInTime": "string",
"estimatedCheckOutTime": "string",
"bookingStatus": "string"
}
}
Comments
0 comments
Please sign in to leave a comment.