> For the complete documentation index, see [llms.txt](https://docs.guibo.travel/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guibo.travel/developers/dynamic-packaging-api.md).

# Dynamic Packaging API

The Dynamic Packaging API enables third party software to generate personalized, high-quality trip itineraries on demand. Designed for modern travel operations, the API turns complex booking data into fully customized travel plans—tailored to each individual customer without sacrificing detail, accuracy, or structure.

While traditional bespoke itineraries require manual assembly or sacrifice quality for speed, the Dynamic Packaging API ensures that every dynamically generated trip delivers the exact same standard of rich documentation, turn-by-turn navigation, and detailed destination insights as a pre-season, professionally published guidebook.

Start at a **destination** (or a **hotel**), find the **routes** that leave from there, see which destination each route ends at, and continue from that destination. 

Base URL: `https://services.schneidergeo.com/content/dynamic-packaging`

### Prerequisites

* **Destination library**: destinations are markers with the icon `destination` stored in your default *Destination library*. Destination library is a library of type Geodata, which you set as your default destination library in the account settings.
* **Route libraries**: Routes must be stored in libraries of type *Geodata*. Shared libraries (libraries that other accounts have shared with you) are included in all searches.
* **Accommodation library**: hotels are markers with the icon `hotel`, `bed_breakfast` or `apartment` in your default accommodation library. Accommodation library is a library of type Geodata, which you set as your default Accommodation library in the account settings.
* **Destination/route linking**: when a route is saved, GUIBO automatically links it to every destination lying within approx. 2 km of its first waypoint (*from*) and its last waypoint (*to*). The endpoints below rely on these links; routes that do not start or end near a destination can still be found with the coordinate search (section I).

In all examples:

* Replace `xxxxxx-xxxxxx-xxxxxx-xxxxxx` with your API key, you can find this under *Account Settings > General Settings > API Key*. The account is derived from the API key; you never pass it explicitly.
* `dddddd`, `hhhhhh` and `rrrrrr` are the internal IDs (the `link` field) of a destination, a hotel and a route.

All responses are JSON (`Content-Type: application/json`). Names and descriptions are language maps (`{"de": "...", "en": "..."}`).

### Typical flow

1. Search the [start hotel ](/developers/dynamic-packaging-api/dynamic-packaging-or-hotel-management.md#a-search-hotels)or [destination](/developers/dynamic-packaging-api/dynamic-packaging-or-destination-management.md#b-list-search-destinations) .
2. Get the outgoing routes [from a hotel](/developers/dynamic-packaging-api/dynamic-packaging-or-route-management.md#b-outgoing-routes-from-a-hotel) or [destination](/developers/dynamic-packaging-api/dynamic-packaging-or-route-management.md#a-outgoing-routes-from-a-destination).
3. The traveller picks a route. If it has an `endDestination`, continue with Step 4 using `endDestination.link`. If not, let the user pick a [connecting route](/developers/dynamic-packaging-api/dynamic-packaging-or-route-management.md#c-outgoing-routes-from-a-coordinate), using the route's last waypoint.
4. Get hotels [near the  destination.](/developers/dynamic-packaging-api/dynamic-packaging-or-hotel-management.md#b-hotels-near-a-destination)
5. Repeat from step 3 until the trip is complete.
6. With all collected data, [create on-demand release](/developers/releases-api/create-on-demand-release.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.guibo.travel/developers/dynamic-packaging-api.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.