> 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/b2b-network/for-resellers/receive-partner-bookings-via-webhook-api.md).

# Receive partner bookings via webhook API

## Precondition

Before being able to access bookings from supplying tour operators you need to be connected with this tour operator on GUIBO ([read more](/publishing/b2b-network/for-resellers/connect-with-tour-operators.md)).

## Why use the webhook?

You likely already have a traveler communication standard for your own products. Reusing those processes for partner bookings normally means a separate integration per partner.

**The webhook is one integration point for all your tour operator partners on GUIBO.** Integrate once — every connected partner delivers bookings to the same endpoint, ready to flow into your existing traveler communication.

## What you receive

When a connected tour operator shares a release with you, GUIBO sends a `POST` request with the release metadata to your endpoint.

Use the **Trip Link** as the access point for your travelers. It gives travelers access to the Tour Guide App, Roadbook PDF, GPX files, and any booking attachments — and stays up to date if your partner has to change booking data later.

{% hint style="info" %}
The webhook complements the [Release Dashboard](https://claude.ai/chat/access-bookings-from-partners.md) and email notification — it does not replace them.
{% endhint %}

## How to set up the webhook

See [developer documentation on B2B Webhook](/developers/releases-api/release-or-b2b-webhook.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.guibo.travel/publishing/b2b-network/for-resellers/receive-partner-bookings-via-webhook-api.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.