> For the complete documentation index, see [llms.txt](https://support.holidayhero.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.holidayhero.com/integrations/pms-platforms/lodgepilot.md).

# LodgePilot

## LodgePilot <a href="#lodgepilot" id="lodgepilot"></a>

<figure><img src="/files/67VMXLB120hHx2NmoB9C" alt=""><figcaption><p>HolidayHero LodgePilot Integration</p></figcaption></figure>

LodgePilot is a property management system for holiday rental and short stay operators, built to keep bookings, guests and availability organised in one place. It is aimed at owners and managers who run a portfolio of rentals and want their reservations to flow automatically into the other tools they use every day. LodgePilot can send each new or updated booking out to connected services the moment it changes, so nothing has to be re typed by hand.

***

**Category:** `PMS`

***

#### Reservation import <a href="#reservation-import" id="reservation-import"></a>

With the LodgePilot integration, your LodgePilot bookings are brought straight into your HolidayHero workspace. Whenever a reservation is created or changed in LodgePilot, it is sent to HolidayHero and turned into a reservation on the matching listing, so the rest of your operation (messaging, tasks, smart devices, reporting) runs on the same set of bookings as LodgePilot.

Each booking is kept in step by its LodgePilot booking reference. The first time HolidayHero sees a booking it creates a new reservation; every time that same booking is sent again it updates the existing reservation instead of duplicating it. If nothing meaningful has changed since the last sync, HolidayHero simply leaves the reservation as it is. LodgePilot can send the same booking more than once, and occasionally out of order, so HolidayHero also checks the timestamp on each update and ignores anything older than what it already has.

What comes across for each booking: the check in and check out dates, the booking number, the rental amount, the number of guests (adults, children and babies), and the lead guest's details (first name, last name, email, phone, country and preferred language).

#### Confirmations and cancellations <a href="#confirmations-and-cancellations" id="confirmations-and-cancellations"></a>

Only confirmed stays become reservations. A booking that LodgePilot still holds as a request or a provisional hold is left alone until it is confirmed, so your calendar never fills up with enquiries that may never happen. The moment it flips to confirmed, it arrives as a normal reservation.

When a booking is cancelled or declined in LodgePilot, the matching HolidayHero reservation is marked cancelled too, and no guest invitation goes out. A booking that is cancelled before HolidayHero ever saw it is simply ignored.

#### Your first import <a href="#your-first-import" id="your-first-import"></a>

You do not start with an empty calendar. As soon as you match your listings and switch the integration on, HolidayHero pulls in the stays you already have in LodgePilot, so your upcoming bookings are there from the first minute. Only stays that have not checked out yet are brought over. LodgePilot does not hand over past stays, so HolidayHero is not a place to look up last season's bookings.

Match a new rental later and the same thing happens for that rental on its own.

#### Keeping things in step <a href="#keeping-things-in-step" id="keeping-things-in-step"></a>

After that first import, changes arrive as they happen: LodgePilot sends each new booking, change and cancellation the moment it occurs, and retries if HolidayHero cannot be reached.

If you ever suspect a rental has drifted out of step, re saving that listing's match on the **Listings** tab pulls its current stays again. Existing reservations are updated rather than duplicated, so it is safe to do at any time.

#### Listings and matching <a href="#listings-and-matching" id="listings-and-matching"></a>

Reservations only import for rentals you have matched. On the **Listings** tab you paste the LodgePilot rental ID next to each HolidayHero listing. That ID is not shown as a field in LodgePilot: you copy it out of the rental's URL in the LodgePilot backoffice. The guide "Where do I find the LodgePilot rental ID?" below walks through it.

Matching does more than label a booking. LodgePilot talks to HolidayHero as one connection shared by everyone, and nothing on a booking says which workspace it belongs to. The rental reference is what settles it: HolidayHero takes the rental on the incoming booking, finds the listing you matched it to, and delivers the reservation to that workspace. Nothing arrives anywhere until you have matched it.

If a booking arrives for a rental nobody has matched, HolidayHero safely ignores it. Match the rental and the next update comes through.

#### Guest invitation <a href="#guest-invitation" id="guest-invitation"></a>

When a reservation comes in and is not cancelled, the lead guest is automatically invited to the HolidayHero guest app, provided they have an email address on the booking. Guests who have already been invited are not invited again, so re syncing a booking never sends a duplicate invite.

#### The LodgePilot connection <a href="#the-lodgepilot-connection" id="the-lodgepilot-connection"></a>

There is nothing to connect or configure yourself. HolidayHero and LodgePilot are connected as partners, with signed and verified traffic between the two platforms, and that connection is shared by every operator who uses both. You do not need a URL, a key or a password.

What you do need is for LodgePilot to switch on your rentals for HolidayHero. Until they do, no bookings are sent for your properties. Ask your LodgePilot contact to enable them.

#### Logs <a href="#logs" id="logs"></a>

The **Logs** tab records every booking HolidayHero receives: which ones were queued, created, updated, skipped (for example, an unmatched rental) and any that failed. It is the place to look when you want to confirm a booking arrived or understand why one did not appear.

***

#### Guides <a href="#guides" id="guides"></a>

<details open>

<summary>How to integrate with LodgePilot?</summary>

**In LodgePilot**

1. Ask your LodgePilot contact to switch on the rentals you want to bring into HolidayHero.

**In HolidayHero**

1. Go to your desired [HolidayHero Workspace](https://admin.holidayhero.com/).
2. Go to [Integrations](https://admin.holidayhero.com/integrations).
3. Select **LodgePilot**.
4. Walk through the authentication process. You are installing an application on top of your HolidayHero workspace.
5. On the **Listings** tab, paste the LodgePilot rental ID next to each HolidayHero listing and save. See the guide below for where to find that ID. This is what tells HolidayHero which bookings are yours, so nothing arrives before you have done it.
6. Activate the integration on the **Home** tab.

From now on, LodgePilot sends each new, updated or cancelled booking to HolidayHero automatically.

</details>

<details open>

<summary>Where do I find the LodgePilot rental ID?</summary>

The rental ID is not shown as a field in LodgePilot. You read it from the address bar while you have the rental open.

1. Open the LodgePilot backoffice.
2. Go to **Rentals**.
3. Click the rental you want to match.
4. Look at the URL and copy the part between `rentals/` and `/overview`, without the slashes.

For this URL:

```
https://lodgepilot-dev.web.app/rentals/856e25d9-e3d4-4dbe-a696-071225826dc8/overview
```

the rental ID is:

```
856e25d9-e3d4-4dbe-a696-071225826dc8
```

<figure><img src="http://localhost:63342/markdownPreview/1393620790//files/PLACEHOLDER" alt="Copying the LodgePilot rental ID from the browser address bar"><figcaption><p>The rental ID sits between <code>rentals/</code> and <code>/overview</code> in the LodgePilot URL</p></figcaption></figure>

Paste that value into the field next to the matching HolidayHero listing on the **Listings** tab and save. Repeat for each rental you want to import.

</details>

<details open>

<summary>Why is a booking not showing up in HolidayHero?</summary>

The most common reason is that the rental has not been matched. The rental match is what routes a booking to your workspace, so an unmatched rental means the booking has nowhere to land. Open the **Listings** tab, match the rental to the right HolidayHero listing and save. Saving the match imports that rental's current stays right away.

The second most common reason is that the booking is not confirmed yet. Requests and provisional holds are held back on purpose and only import once LodgePilot confirms them.

Also check that the integration is switched on. If the toggle on the **Home** tab is off, incoming bookings are received but deliberately not processed, and the reason is noted on the Logs tab.

Finally, check with LodgePilot that the rental is switched on for HolidayHero on their side. Nothing is sent for a rental they have not enabled.

</details>

<details open>

<summary>A booking was cancelled in LodgePilot but still shows in HolidayHero</summary>

Cancellations come across the same way as any other change, so the reservation should be marked cancelled within moments. If it has not, check the Logs tab. A cancellation for a booking HolidayHero never imported (for example, one that was cancelled while the rental was still unmatched) is skipped on purpose and noted there.

</details>

<details open>

<summary>A booking arrived in the wrong HolidayHero workspace</summary>

A LodgePilot rental should be matched in one workspace only. If the same rental is matched in two, the booking is delivered to both, because the rental match is the only thing that says where a booking belongs. Open the **Listings** tab in the workspace that should not have it and clear the match.

</details>

<details open>

<summary>What happens if LodgePilot is temporarily unavailable?</summary>

Temporary problems (timeouts, gateway errors and other transient failures) are retried automatically by HolidayHero before a booking is ever marked as failed. Permanent errors are written to the **Logs** tab together with the details, so you can investigate.

</details>

***

**HolidayHero Permissions**

Each integration has its own set of permissions. Please find below what this integration will be able to do.

<table><thead><tr><th width="259">Permission</th><th>Description</th></tr></thead><tbody><tr><td><code>reservation.create</code></td><td>The integration will be able to create reservations imported from LodgePilot.</td></tr><tr><td><code>reservation.update</code></td><td>The integration will be able to update reservations when they change in LodgePilot.</td></tr><tr><td><code>listing.read</code></td><td>The integration will be able to read your listings so you can match them to LodgePilot rentals.</td></tr><tr><td><code>invitation.create</code></td><td>The integration will be able to invite the lead guest to a reservation.</td></tr></tbody></table>

**HolidayHero Webhooks**

<table><thead><tr><th width="260">Webhook</th><th>Description</th></tr></thead><tbody><tr><td><code>listing.deleted</code></td><td>The integration detects when a listing has been removed and will remove the corresponding matched listing.</td></tr><tr><td><code>installation.uninstalled</code></td><td>The integration cleans up its data when it is uninstalled from your HolidayHero workspace.</td></tr></tbody></table>

***

## Agent Instructions: Querying This Documentation <a href="#agent-instructions-querying-this-documentation" id="agent-instructions-querying-this-documentation"></a>

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://support.holidayhero.com/integrations/pms-platforms/lodgepilot.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.