Releases API
The Releases API connects your booking system with GUIBO to automatically publish personalized travel documents for every booking — without any manual work.
Why Automate with the Releases API?
Without automation, someone on your team must manually create a release in GUIBO for every single booking: entering the download code, selecting the guidebook, setting dates, adding hotels, and attaching documents. For 500+ bookings per season, that's a significant time investment and a source of errors.
The Releases API eliminates this by letting your booking system talk directly to GUIBO:
Manual release creation per booking
Automatic release creation when booking is confirmed
Copy-paste hotel details from booking system
Hotels automatically assigned per booking
Manually attach vouchers and documents
Documents automatically attached
Risk of errors and delays
Instant, error-free publishing
Staff time spent on repetitive tasks
Staff focuses on product quality
What Does "Personalized" Mean?
Every traveler receives travel documents tailored to their specific booking:
Accommodations — The exact hotels for this booking, with arrival/departure dates and comments like "Breakfast included" or "Late check-out confirmed"
Documents — Booking-specific PDFs such as hotel vouchers, train tickets, or rental agreements
Access period — Content is available exactly when the traveler needs it
Agency branding — When booked through a reseller, travel documents automatically appear in the reseller's brand
Common Use Cases
1. Automated release creation from your booking system
Your booking system sends booking data to GUIBO → GUIBO creates a personalized release → Traveler receives their Trip Link with all travel docs.
2. Personalized hotel lists per booking
Each traveler sees only their specific hotels with check-in/check-out dates and booking comments — not a generic list.
3. Booking-specific documents
Automatically attach PDFs like hotel vouchers, train tickets, or insurance documents to individual bookings.
4. Reseller automation
When a booking comes through a reseller, set the reseller as "seller" on the release. GUIBO automatically rebrands all travel documents to the reseller's look and feel. You can also define a specific seller download code so that both parties can find the release with their own reference number — the operator uses the operator download code (typically your booking reference), while the reseller uses the seller download code (typically their booking reference).
Two Ways to Create Releases via API
Guidebook Release
Standard tours with a fixed itinerary
Creates a release based on an existing guidebook. You personalize with hotels, documents, and dates.
On-demand Release
Tailor-made trips where every booking is different
Creates both guidebook and release in a single API call. Full flexibility over routes, POIs, and text per booking.
Most tour operators start with guidebook releases — they cover the majority of use cases and are simpler to implement.
What You Can Do With the Releases API
Automatically create releases when bookings are made
Retrieve details of existing releases
Update release information to reflect booking changes
Revoke releases when bookings are canceled
Add or remove documents from existing releases
Getting Started
To use the Releases API, you'll need:
A GUIBO account with API access enabled
Your API credentials (available in your account settings under Account Settings → General Settings → API Key)
A developer or IT partner with basic understanding of RESTful API interactions
No developer in-house? Many tour operators work with their booking system provider or a freelance developer to set up the integration. The GUIBO team can support with technical onboarding.
Each endpoint is documented in detail on its respective page, with request examples and response formats to help you implement quickly.
Last updated