Duve has integrated with IglooHome, 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 IglooHome via IglooBridge, 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 IglooHome 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 IglooHome, enabling a smooth and secure room access process.
Duve will send all the events to IglooHome, and IglooHome 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 IglooHome integration.
How to Set Up the DuveConnect-IglooHome Integration
Setup Steps
- Access Webhook Settings: In the Duve dashboard, navigate to Settings > Connections > DuveConnect.
-
Click on the "Outgoing" tab and set Up Webhooks: Click on "Create New Connection" to add IglooHome as an integration.
- Pre-Check-In Done
- Pre-Check-Out Done
- Room Changed on Reservation
- Reservation Status Changed
- Stay Dates Updated
-
Create a new Incoming Connection:
- Create an Additional Field for the Reservation, Type = Text
- Select `add new` inside the additional fields, and add a "Pin" field.
- Create it and remember the bolded text. In this case, it would be: igloo-adom_pin_uYE9YfX9aC. This will be referred to in the spreadsheet as `Duve Pin Field`
- Replicate the steps for `pin_first_usage` as well. The bolded text will be referred to in the spreadsheet as `Duve Pin First Usage Field`
- Create a new "Incoming" connection, in the "DuveConnect" tab, named Igloohome, in order for Igloohome to send the codes correctly to Duve.
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.
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. 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"
}
}
4. 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"
}
}
5. 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"
}
}
Setup Incoming Connection
- Open the "Incoming"
- Select `Create New Connection` and add the name Igloohome.
- Copy the Access Token and the Request Example, by clicking the `Show` and `Copy` button and send these to Igloohome's team. They will complete the setup and let you know when it is live.
- Below Access Scopes, select these data points:
Reservation details > Primary Code
Additional Fields > pin
Additional Fields > pin_first_usage (The additional fields created in the beginning). - Save the Incoming connection ID:
On the URL, there should be a random number and string combination. Such as `...duve.com/privateapps/67ff41c1ec4927bc3042165e`, copy the endpoint portion "67ff41c1ec4927bc3042165e", and share it to the IglooHome team, as the "Incoming PID"
Common Error - Missing Estimated Check-In Time
Error Description:
A frequent error encountered during webhook triggers is the missing estimatedCheckInTime field in the payload, leading to a failed webhook request.
Sample Error Response:
{
"IsSuccess": false,
"Message": "Missing required fields in resource : estimatedCheckInTime"
}
Resolution:
Ensure that the estimatedCheckInTime field is populated in the payload to prevent webhook failure.
Comments
0 comments
Article is closed for comments.