> 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/how-to-publish/create-releases.md).

# Create releases

Create releases from guidebook templates or on-demand via API, personalize them per booking, and cancel when needed.

This page shows the two ways to define release content, how release creation is triggered, and how to personalize or cancel a release.

## Template-based releases vs on-demand releases

{% columns %}
{% column %}

### Template-based releases

The release is created from a pre-existing guidebook in GUIBO. Booking-specific data is added during release creation: accommodation bookings, PDF attachments, and any other guidebook customization.

#### When to choose?

Choose **template-based** when all bookings of a product share the same itinerary — the guidebook serves as the template, and only accommodations and documents vary per booking.

#### Creating template based releases

* **Web portal** — manually, by users in the release dashboad
* **API** — automated, typically triggered from a booking system. Click here for the [release API](/developers/releases-api.md) here.
  {% endcolumn %}

{% column %}

### On-demand releases

The release is created without a pre-existing guidebook — the guidebook is defined dynamically as part of the release creation. Source content can be provided from external systems or from GUIBO libraries.

#### **When to choose?**

Choose **on-demand** when the itinerary differs from booking to booking, e.g. tailor-made trips assembled in an external trip builder. See Integrate External Content for a full comparison.

#### **Creating on-demand releases**

* **API** — automated, typically triggered from a booking system. Click here for the [on-demand API](/developers/releases-api/create-on-demand-release.md).
  {% endcolumn %}
  {% endcolumns %}

## Personalizing template-based releases

Releases are always booking specific with booking related content. See the table below to understand all available options:

<table><thead><tr><th width="198.55078125">Content type</th><th>Personalization options</th></tr></thead><tbody><tr><td><strong>Guidebook</strong></td><td><p>You can modify the guidebook of template-based releases which creates a guidebook copy in order to make changes for one booking only.</p><p>Customizing on-demand releases is typically not required as all content is booking-specific already.</p></td></tr><tr><td><strong>PDF Documents</strong></td><td>Attach any PDF Documents to a release and decide how travelers can access: Via Tour Guide App and/or Trip Link.</td></tr><tr><td><strong>Accommodation Bookings</strong></td><td>Add any accommodation bookings to a release with a POI, arrival/departure date and booking comments.</td></tr><tr><td><strong>Roadbook PDF</strong></td><td>Roadbook PDFs are available only for template-based releases. Any customizations made to a guidebook are not reflected in the Roadbook PDF. Roadbook PDFs are currently unavailable for on-demand releases.</td></tr><tr><td><strong>GPX Download</strong></td><td>Choose whether you want to offer GPX files via Trip Link for download to your travelers. The GPX files reflect the routes included in the release’s guidebook.</td></tr></tbody></table>

## Cancel a release

A release cannot be deleted. Cancel it in the **Release Dashboard** by changing `Status` from **active** to **canceled** — possible only before the download period starts.

{% hint style="info" icon="triangle-exclamation" %}
The download code of a canceled release remains blocked and cannot be reassigned.
{% endhint %}

### Next step

Share the [Trip Link](/publishing/trip-link.md) with your travelers — their central access point to all travel documents.


---

# 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.guibo.travel/publishing/how-to-publish/create-releases.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.