# Getting Started

### URL structure

Every journey is available at a URL unique to your integration:

```
https://xcj.xcover.com/{partner}/{lang}/
```

<table><thead><tr><th width="124.09765625">Segment</th><th width="480.41796875">Description</th><th>Example</th></tr></thead><tbody><tr><td><code>{partner}</code></td><td>Your partner slug, assigned by Cover Genius during onboarding</td><td><code>acme-travel</code></td></tr><tr><td><code>{lang}</code></td><td>ISO 639-1 language code</td><td><code>en</code></td></tr></tbody></table>

### Environments

<table><thead><tr><th width="289.56640625">Environment</th><th>URL pattern</th></tr></thead><tbody><tr><td>Sandbox — Integration testing with test data</td><td><code>https://sandbox.xcj.xcover.com/{partner}/{lang}/</code></td></tr><tr><td>Production — Live customer traffic</td><td><code>https://xcj.xcover.com/{partner}/{lang}/</code></td></tr></tbody></table>

{% hint style="info" %}
Use the sandbox environment during development. Sandbox accepts test payment credentials and does not issue real policies.
{% endhint %}

### Prerequisites

Confirm the following with your Cover Genius integration manager before starting:

* **Partner slug** — your unique identifier in the journey URL
* **Sandbox access** — credentials for the sandbox environment
* **Allowlisted domains** — your domains must be allowlisted for iframe embedding
* **Authentication model** — whether your integration uses OAuth consent, SSO, or unauthenticated access
* **Branding assets** — logo, brand colors, and fonts for white-labelling


---

# Agent Instructions: 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:

```
GET https://partner-docs.covergenius.com/home/xcover-journeys/integration/getting-started.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.