> For the complete documentation index, see [llms.txt](https://docs.guibo.travel/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guibo.travel/publishing/tour-guide-app/personalized-accommodation.md).

# Personalized Accommodation

Each release can carry **booking-specific accommodation details**. Travelers see them in the Tour Guide App in two ways: In the accommodation list as well as within the stages as check-in and check-out accommodation.

## Add booking specific accommodations to your releases

{% tabs %}
{% tab title="Web portal" %}

1. Go to the **Release Dashboard** and open the release.
2. At the bottom right, open the **Accommodation** tab.
3. Add or review the accommodations for this release.
4. Provide **arrival date**, **departure date**
5. Optionally, provide any **booking comment**

<figure><img src="/files/okKdN4Iwly0ftWVJ6bqC" alt="" width="375"><figcaption><p>How to add accommodations in the release dashboard</p></figcaption></figure>
{% endtab %}

{% tab title="API" %}

#### **1. Trip arrival and departure dates**

Include booking dates for the overall trip when creating the release:

```json
...
"arrivaldate":"2025-01-22",
"departuredate": "2025-01-25"
...
```

#### **2. Accommodation details**

Provide arrival date, departure date, and any comment along with the accommodation POI:

```json
...
 "accommodation": [
           {
               "externalId":"HPO1",
               "libraryExternalId":"HOTELS",
               "arrivalDate":"2025-09-05",
               "departureDate":"2025-09-06",
               "comment":"A generous breakfast buffet is included"
           }
       ]
```

See the developer area or [click here](/developers/releases-api/release-or-create-guidebook-release.md#b-create-download-permission-with-customization) for an end-to-end example on how to create a release with booking specific accommodation information via API.
{% endtab %}
{% endtabs %}

## What travelers see

{% columns %}
{% column %}

#### Accommodation List

Personalized accommodation list easily accessible from the trip's home screen.

**All accommodations are shown here.**

<div align="center"><figure><img src="/files/YsfIJvrYkXHMiIkZd95y" alt="" width="188"><figcaption><p>Accommodation List in the Tour Guide App</p></figcaption></figure></div>
{% endcolumn %}

{% column %}

#### Within Stages

Check-in and check-out accommodation within each day-by-day stage.

[**Click here on how to configure**](/publishing/tour-guide-app/personalized-accommodation/stage-matching.md)

<figure><img src="/files/YSuqntIsddhEWJVrURp5" alt="" width="188"><figcaption><p>Check-in &#x26; check-out accommodations per day</p></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

### Choose your layout

How hotels appear in the app depends on **how your stages are structured**. Find your case below:

<table><thead><tr><th width="360">Your stages are…</th><th>Hotels shown on each stage?</th></tr></thead><tbody><tr><td><strong>Travel days</strong> — a different hotel each night (classic point-to-point tour)</td><td><strong>Yes</strong> — each day shows its check-in and check-out hotel</td></tr><tr><td><strong>Travel days</strong> — the same hotel every night (a "star" trip from one base)</td><td><strong>Yes</strong> — each day shows the hotel, so travelers have everything for that day in one place</td></tr><tr><td><strong>Curated collections</strong>, not days — restaurants, routes, experiences</td><td><strong>No</strong> — hotels appear only under the <strong>Accommodation</strong> list in the app</td></tr></tbody></table>

When your stages are travel days, GUIBO places the right hotel on each day automatically, using **destination points** in the guidebook (set these up below). When they are curated collections, you simply switch the per-stage display off — travelers still get every hotel in the app's accommodation overview.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.guibo.travel/publishing/tour-guide-app/personalized-accommodation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.