> For the complete documentation index, see [llms.txt](https://docs.guestway.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guestway.io/integrations/property-management-systems/apaleo.md).

# How to connect Apaleo

This guide shows you how to connect an Apaleo property to Guestway, and how to set up email forwarding for Booking.com messages.

{% hint style="info" %}
**Before you start**

* You have the **Super admin** role.
* The property code of your Apaleo property.
* An Apaleo login that can allow apps for the property. To link your Apaleo users to Guestway, use a login that can see the users of the Apaleo account.
  {% endhint %}

## Connect the account

{% stepper %}
{% step %}

### Open the integrations

Go to **Settings** → **Organization** → **Integrations** and click **Create**.
{% endstep %}

{% step %}

### Choose Apaleo

Under **Property Management Systems**, click **Apaleo**.
{% endstep %}

{% step %}

### Enter the property

In **Integration name**, keep the suggested name or enter your own. In **Property ID**, enter the property code. You find it in the address of the Apaleo settings page: `https://app.apaleo.com/MY_PROPERTY_CODE/settings/general`.

You cannot change the property ID later. For another property, add another integration.
{% endstep %}

{% step %}

### Sign in to Apaleo

Click **Secure Login via OAuth2**, then **Authenticate**. Sign in to Apaleo and allow Guestway access. Apaleo sends you back to Guestway.
{% endstep %}
{% endstepper %}

## Set up email forwarding

Apaleo does not send guest messages, so messages from Booking.com reach Guestway by email. The wizard shows the step **Email Forwarding**.

{% stepper %}
{% step %}

### Copy the receiving email

Copy the **Receiving email**. You add it in Booking.com later. See [How to connect Booking.com](/integrations/online-travel-agencies-ota/booking.com.md).
{% endstep %}

{% step %}

### Enter a forwarding email

In **Forwarding email**, enter an address of yours. Guestway forwards a copy of every email it receives to it.

{% hint style="success" %}
Set a forwarding email. If a message seems to be missing in Guestway, you can check in this inbox whether it reached Guestway at all.
{% endhint %}
{% endstep %}

{% step %}

### Finish

Click **Save and continue**, then **Finish**.

To do this later, click **Skip for now**. You then find both fields on the integration, in the card **OTA Messaging System**.
{% endstep %}
{% endstepper %}

## Troubleshooting

<details>

<summary>Why are my Apaleo users not linked to Guestway users?</summary>

Guestway links Apaleo users only when the Apaleo login used to connect can see the users of the Apaleo account. Open the integration, click **Re-authenticate**, and sign in with such a login.

</details>

## Related

* [Apaleo billing](/integrations/property-management-systems/apaleo/apaleo-billing.md)
* [What syncs from your PMS](/integrations/property-management-systems/what-syncs-from-your-pms.md)
* [Integrations](/integrations/integrations.md): every field and action
* [How to choose which listings and devices sync](/integrations/integrations/how-to-choose-which-listings-and-devices-sync.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.guestway.io/integrations/property-management-systems/apaleo.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.