> For the complete documentation index, see [llms.txt](https://partner-docs.covergenius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://partner-docs.covergenius.com/xcover-journeys/integration/web-embedding-iframe.md).

# Web Embedding (iframe)

How to embed an XCover Journey in an iframe on your website.

Add an iframe to your page with the journey URL:

```html
<iframe
  id="xcover-journey"
  src="https://sandbox.xcj.xcover.com/acme-travel/en/"
  style="width: 100%; height: 800px; border: none;"
></iframe>
```

{% hint style="warning" %}
Replace `acme-travel` with your partner slug and update the language and country codes for your integration. When going live, switch the URL from `sandbox.xcj.xcover.com` to `xcj.xcover.com`.
{% endhint %}

### Domain allowlisting

If your site uses a Content Security Policy (CSP), ensure that `xcj.xcover.com` (and `sandbox.xcj.xcover.com` for testing) is allowed in your `frame-src` or `child-src` directive. Without this, the browser will block the iframe from loading.

### Sandbox attribute

If you use the `sandbox` attribute on the iframe, include these values to avoid breaking the journey:

```html
sandbox="allow-scripts allow-forms allow-popups allow-same-origin"
```

* `allow-scripts` — the journey is a JavaScript application
* `allow-forms` — customer data entry and payment forms require form submission
* `allow-popups` — authentication flows may navigate to external domains from within the iframe
* `allow-same-origin` — session storage requires same-origin access

{% hint style="warning" %}
Omitting any of these will break the journey.
{% endhint %}


---

# 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://partner-docs.covergenius.com/xcover-journeys/integration/web-embedding-iframe.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.