# When using on-demand releases

## When to use this

Your external system controls the complete trip structure per booking. No guidebooks in GUIBO needed — each release is created from a single API call.

Continue reading [here](https://docs.guibo.travel/content-management/integrate-external-content/broken-reference), when you manage routes, POIs, or text content in a third-party system but want to use that data as building blocks in GUIBO to manage your guidebooks.

## How it works

Your booking or trip planning system already knows the full itinerary — which routes, which hotels, which stages. When a booking is confirmed, your system sends this information to GUIBO. GUIBO then generates a booking based release in one step. There is no need to set up or maintain guidebooks in GUIBO — everything is driven by your external system.

Itinerary data can grow to several hundred megabytes when routes, POI images, and text content are sent inline for every booking. In order to improve reliability, save costs and energy, we recommend to sync assets (e.g. routes, POIs) which are reused across many bookings into libraries. Referencing them by ID reduces each API request to a fraction of that size.

### Two options for content delivery

| Option                                     | How it works                                                                               | When to use                                                                  |
| ------------------------------------------ | ------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------- |
| **Send all content inline**                | Routes, POIs, text pages are included directly in the API payload per release              | Content is unique per booking, or data volumes are small                     |
| **Reference content from GUIBO libraries** | The API payload references assets by ID from synced libraries — GUIBO resolves the content | Reusable content (routes, POIs, images) is large and repeats across bookings |

**Example:** Instead of sending a 50 MB route inline for every booking, sync the route once into a library and reference it:

```json
"libraryReference": {
  "libraryCustomId": "MY_ROUTES_LIB",
  "customId": "RT_233"
}
```

## Setup with library references

1. [Set up library sync](https://claude.ai/chat/set-up-library-sync.md) — sync reusable content from your external system into GUIBO libraries
2. Use `libraryReference` in your on-demand release payloads to reference the synced assets

## Next step

See [Create on-demand release](https://claude.ai/developers/releases-api/release-or-create-guidebook-release/create-on-demand-release.md) for the complete API reference, including inline and library reference examples.