Set up library sync

How to sync routes, POIs, and text pages from a third-party system into GUIBO libraries — so your external system stays the single source of truth.

How it works

Your external system pushes data into GUIBO libraries via the Content API. Once synced, the libraries work exactly like manually managed ones — they can be imported into guidebooks or referenced in on-demand releases.

1. Create libraries in GUIBO

Set up your library structure. We recommend to organize libraries by type (routes, POI, textpages) and data source. For example:

• Routes GUIBO — routes maintained in GUIBO

• Routes MY GEO CMS — four routes synched from GEO CMS

• POI MY GEO CMS— sights, restaurants, services

• Accommodations MY BOOKING SYSTEM — hotels, guesthouses

• Text pages GUIBO — info pages, FAQs, arrival instructions managed in GUIBO

2. Use custom IDs consistently

Every asset in GUIBO can carry a custom ID (customId in the API). Assign the same ID that your source system already uses. This is what allows the sync to identify and update assets in GUIBO directly.

3. Implement the sync

Your developer or system provider sets up a sync job (typically nightly) that pushes data into the libraries.

The sync should follow an update-first approach for each asset in the source system:

1. Try to update the asset in GUIBO with your custom ID

2. If not found → create it as a new asset

This ensures that every sync run both updates all existing assets and adds new ones — GUIBO always reflects the current state of the source system.

The Content API provides separate endpoints for creating and updating each content type. For example, POIs:

Operation	Method	Endpoint
Create	POST	/content/geodata/poi
Update	PUT	/content/geodata/poi/{account}/{libraryId}/{id}

See the Content API for all endpoints.