> For the complete documentation index, see [llms.txt](https://docs.flip.to/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flip.to/docs/integrations/booking-engines/vendors/reztrip.md).

# RezTrip

Adding Flip.to to your RezTrip booking engine takes one line of code.

***

## Add the snippet

Copy and paste the snippet below into the **\<head> tag** of every page of your RezTrip booking engine, **including the confirmation page**.

```html
<script async src="https://integration.flip.to" crossorigin="anonymous"></script>
```

The same line goes on your website—see [Set up your website](/docs/integrations/websites/set-up-your-website.md).

***

## Configurations

<details>

<summary>Single-page applications</summary>

Load the snippet at application start, not on virtual pageviews.

</details>

<details>

<summary>Overriding what Flip.to detects (rarely needed)</summary>

For a custom booking-engine domain, or a page whose language markup is wrong or missing. See [Overrides](/docs/integrations/booking-engines/set-up-your-booking-engine.md#overrides) on Set up your booking engine.

</details>

<details>

<summary>Tracking add-ons and other products</summary>

If you sell experiences, events or ancillary items at time of booking, those still need to be passed to Flip.to—see [E-commerce tracking](/docs/integrations/booking-engines/e-commerce-tracking.md).

</details>

***

If we can be of any help, say hello to our [Customer Success team](/docs/support/customer-success.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.flip.to/docs/integrations/booking-engines/vendors/reztrip.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.