> 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/developers/releases-api/how-to-create-releases-for-bookings-per-api.md).

# HOW TO create releases for bookings per API

Releases allow you to package and deliver trip information directly to your customers. Depending on your workflow and the level of customization required, GUIBO offers two ways to create a release:

### 1. Guidebook-Based Releases (Standard)

Use this option when you have a pre-configured Guidebook template ready for a specific trip or itinerary.

* Best for: Standardized trips, group travel, or common itineraries.
* How it works: Start with a master Guidebook containing your pre-assembled Stages, Routes, POIs, and general information.
* Customization: Once applied to a booking, you can tailor the release to the customer's needs by:
  * Adding or removing specific Routes and POIs.
  * Attaching booking-specific accommodations and travel documents.

Steps:

1. [Create guidebook per API](/developers/content-api/how-to-create-guidebooks-per-api.md)
2. [Create guidebook release](/developers/releases-api/release-or-create-guidebook-release.md)

### 2. On-Demand Releases (Custom)

Use this option when a booking is highly tailored and starting from a standard package doesn't fit the itinerary.

* Best for: Fully custom, one-off, or highly individualized trips.
* How it works: Build a bespoke Guidebook from scratch directly within the booking.
* Customization: You can:

  * Hand-pick individual assets directly from your master library.
  * Create and upload custom content specifically for this single release.

💡 Best Practice: Reference a guidebook to apply its settings and title image. This also enables centralized analytics tracking in your guidebook.

Steps:

1. [Create on-demand release](/developers/releases-api/create-on-demand-release.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.guibo.travel/developers/releases-api/how-to-create-releases-for-bookings-per-api.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.