Releases

Every booking gets a release — the container for the guidebook, accommodations, documents, and access settings.

What is a release?

A release is the booking-specific unit of publishing in GUIBO: every booking gets its own release, and this page explains what it contains and which settings control traveler access.

Release components

Component	Contents
Guidebook	The full itinerary data — every part of it can be customized per booking.
Accommodation bookings	The booked accommodations with arrival date, departure date, and booking-specific comments.
PDF attachments	Booking-related PDF documents (e.g. vouchers, tickets) delivered to travelers via the Trip Link and in the Tour Guide App.
Metadata	All settings that control access — see below.

Release creation types

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.

Create template-based releases via:

• Web portal — manually, by users

• API — automated, typically triggered from a booking system

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.

On-demand releases are created via API only.

Which create type fits my setup?

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.

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.

Release metadata

Field	Description
ID	Unique ID of the release
Guidebook	Name of the guidebook attached to this release
Operator	GUIBO account operating this booking
Operator Code	Traveler download code for the operator — typically the operator's booking number
Seller	GUIBO account selling this booking
Seller Code	Traveler download code for the seller — typically the seller's booking number
Download period	Time window during which the traveler has access to the guidebook
Max devices	Maximum number of devices that can download the guidebook via the Tour Guide App — typically the number of travelers
Language	Language of the release
Status	Status of the release. A release is downloadable only while status is active.
Publishing App	Traveler download option for the Tour Guide App
Publishing PDF	Traveler download option for the Roadbook PDF via Trip Link
Publishing GPX	Traveler download option for GPX files via Trip Link
Trip Link	The traveler's link to access all booking-related trip information

Next step

Continue with Create a release to see how releases are created — manually or automated per booking.

A release is the booking-specific unit of publishing in GUIBO: every booking gets its own release, and this page explains what it contains and how it is created.

What a release consists of

Component	Contents
Guidebook	The full itinerary data — every part of it can be customized per booking.
Accommodation bookings	The booked accommodations with arrival date, departure date, and booking-specific comments.
PDF attachments	Booking-related PDF documents (e.g. vouchers, tickets) delivered to travelers via the Trip Link and in the Tour Guide App.
Metadata	All settings that control access — see here.

How releases are created

Template-based releases

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

Create template-based releases via:

• Web portal — manually, by users

• API — automated, typically triggered from a booking system

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 come from external systems or from GUIBO libraries.

On-demand releases are created via API only.

Which creation method fits my setup?

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.

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.

Related pages

• How to publish — publishing channels and methods

• Trip Link — the traveler's central access point

• Releases API — automate release creation

A release is a traveler-specific instance of your guidebook that:

• Represents a single booking

• Contains personalized information for specific travelers

• Provides access through multiple delivery channels

• Is active during a defined time period

• Is accessed via unique download codes

Publishing Channels

Each release automatically generates content across multiple channels:

Channel	Description	Availability
Trip Link	Central access point with unique web link for this release	Always included
Tour Guide App	Mobile app with offline maps, navigation, and real-time updates	Always included
Roadbook PDF	Print-ready travel document with maps and itinerary details	Optional
B2B Network	Share releases with resellers so they can forward a re-branded Trip Link to the traveler	Optional
TourMaps	Interactive maps for webshop integration (guidebook-level, not booking-specific)	Always available

Publishing Methods

Manual Publishing

Create releases individually through the GUIBO web portal:

1. Navigate to Release Dashboard

2. Click the orange + button

3. Enter booking details

4. Optionally add personalized content

5. Share the Trip Link with travelers

Best for: Small operations, testing, or individual bookings

API Publishing

Automate release creation from your booking system:

• 100% automated publishing process

• Real-time release generation

• Personalized content per booking

• Scalable for high booking volumes

Best for: Integration with booking systems, high-volume operations

Learn more: Releases API

Release Types

Guidebook-based Releases

Create releases from existing guidebooks:

• Guidebook serves as product template

• Updated seasonally in GUIBO

• Personalized per booking (accommodations, documents, dates)

• Same structure for all bookings of this product

Best for: Standardized tours with consistent itineraries

Learn more: Release | Create guidebook release (via API)

On-demand Releases

Generate complete guidebook and release simultaneously via API:

• Fully dynamic guidebook structure

• Created per booking from JSON payload

• No pre-existing guidebook required

• Maximum flexibility for unique itineraries

Best for: Tailor-made trips, highly variable tours, third-party system integration

Learn more: Create on-demand release

Personalization Options

All releases support booking-specific customization:

• Accommodations with arrival/departure dates and comments

• Additional documents (vouchers, tickets, confirmations)

• Custom content (POIs, routes, text pages)

• Modified content from the base guidebook

Learn more: Personalized Accommodation, Release | Create guidebook release (via API)

Canceling a Release

A Release cannot be deleted. However, you can cancel a release in the release dashboard by changing the status from ACTIVE to CANCELED, provided that the download period has not yet started. Please note that the code will remain blocked and cannot be reassigned.