> 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/mobile-embedding-webview.md).

# Mobile Embedding (WebView)

How to load an XCover Journey in a WebView within your native or cross-platform app.

The journey is a standard web page — no SDK or bridge library is required. Load the journey URL in your platform's WebView component:

```
https://sandbox.xcj.xcover.com/acme-travel/en/?country=AU
```

{% 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 %}

### WebView requirements

Your WebView must meet the following requirements for the journey to function correctly:

* **JavaScript enabled** — the journey is a client-side application
* **DOM storage enabled** — the journey stores state between steps in session storage
* **Third-party cookies allowed** — may be required for authentication flows (OAuth, Auth0)
* **Navigation redirects supported** — authentication uses full-page redirects within the WebView; ensure your WebView handles navigation without opening an external browser

### Platform documentation

Refer to your platform's WebView documentation for setup:

* iOS — [WKWebView](https://developer.apple.com/documentation/webkit/wkwebview)
* Android — [WebView](https://developer.android.com/reference/android/webkit/WebView)
* React Native — [react-native-webview](https://github.com/react-native-webview/react-native-webview)
* Flutter — [webview\_flutter](https://pub.dev/packages/webview_flutter)


---

# 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/mobile-embedding-webview.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.