Content API

Create and update routes, POIs, text pages, and libraries in GUIBO from external systems — mirror your content data without manual maintenance.

Content API

The Content API handles content data — the reusable building blocks of your travel products: routes, POIs, text pages, libraries, and guidebooks. This data is static and maintained season to season, not per booking.

When to use the Content API

You already manage geo data or text content in a third-party system and want to mirror it into GUIBO libraries — so you maintain it in one place only, with no copies that drift out of sync.

For the full integration workflow, see Data Integration.

Endpoints

Endpoint	Purpose
Create library or guidebook	Create the containers that hold your content
Create day/stage	Add day/stage categories to guidebooks
Create and update POIs	Sync hotels, sights, restaurants, services
Create and update routes	Sync cycling, hiking, or transfer routes
Create text page	Sync info pages, FAQs, arrival instructions

How it connects

Content created via this API is used in two ways:

1. Imported into guidebooks — manually or dynamically (auto-import POIs near routes)

2. Referenced in releases — the Releases API adds booking-specific data on top of this content