> 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/publishing/trip-link.md).

# Trip Link

Trip Link provides travelers with one personalized URL to access all travel documents: Tour Guide App, Roadbook PDF, GPX files, and booking attachments.

### What is a Trip Link?

A **Trip Link** is a unique URL generated for each booking. It gives travelers access to all their travel documents in one place — personalized and always up to date.

| Content            | Description                                 |
| ------------------ | ------------------------------------------- |
| **Tour Guide App** | Download link with pre-filled access codes  |
| **Roadbook PDF**   | Print-ready travel document                 |
| **GPX Files**      | Route files for external navigation devices |
| **Documents**      | Vouchers, tickets, and other attachments    |

{% hint style="info" %}
Trip Links stay up-to-date automatically. When the release is updated, travelers see the changes immediately.
{% endhint %}

### How Trip Links Are Created

In GUIBO, each booking is represented by a **release**. When a tour operator creates a release, GUIBO automatically generates a Trip Link. All Trip Links are accessible in your **Release Dashboard**.

### Sharing Trip Links with Resellers

Every release has an assigned **operator** and an assigned **seller**. When you set a seller other than yourself, the Trip Link is automatically rebranded to match the seller's look and feel.

| Reseller Scenario                         | What to Do                                                                                                                       |
| ----------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| **Reseller has a GUIBO account**          | Set them as seller — done. They receive an email notification and see the release in their Dashboard.                            |
| **Reseller is not on GUIBO yet**          | Send them an invitation to create a free GUIBO account for seamless collaboration.                                               |
| **Reseller doesn't want a GUIBO account** | Set yourself as seller or create a self-managed brand for rebranded Trip Links and send the Trip Link manually to your reseller. |

{% hint style="info" %}
**Recommended:** Invite your resellers to create a free GUIBO account. This eliminates manual link sharing and ensures automatic notifications for every new booking.
{% endhint %}

### Learn More

* [How to publish?](/publishing/how-to-publish/how-to-publish.md)
* [B2B Network](/publishing/b2b-network.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/publishing/trip-link.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.