> 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/offers/vertical-examples/property-renters.md).

# Property / Renters

Commonly, partners will integrate XCover using two key purchase process API calls: [create offer](/offers/guides/purchase-workflow-overview/create-offer.md) and [confirm offer](/offers/guides/purchase-workflow-overview/confirm-offer.md).\
\
Most integrations follow the below high level flow of events:

<figure><picture><source srcset="/files/4YSDEOLrOwzbmMnOEbCl" media="(prefers-color-scheme: dark)"><img src="/files/weoCDm6ZVUFAvyGO1Sr9" alt=""></picture><figcaption></figcaption></figure>

1\. User goes through a property related User Experience\
2\. Partner platform sends an [offer payload](/offers/guides/purchase-workflow-overview/create-offer.md) to the create offer endpoint\
3\. User selects offer product/s\
4\. User pays for travel and offer at checkout\
5\. [Payment collection](/offers/guides/payment-process.md)\
6\. Partner sends a [confirmation request payload](/offers/guides/purchase-workflow-overview/confirm-offer.md) to the confirm offer endpoint\
7\. XCover sends confirmation email including policy details, Partner sends purchase confirmation and tax invoice.

#### Post sale processes

[Modification](/offers/guides/purchase-workflow-overview/modify-booking.md)\
Changes to customer details such as name, address, or any rating factor needs to be captured in order to ensure the customer is paying the appropriate premium.

<figure><picture><source srcset="/files/SQU9mJkRnt3F7mKpeync" media="(prefers-color-scheme: dark)"><img src="/files/vkIKDFMcnfp2AxvPdC0l" alt=""></picture><figcaption></figcaption></figure>

\
[Cancellation](/offers/guides/purchase-workflow-overview/cancel-booking.md)\
Should a partner need to facilitate policy cancellation, the below workflow should be referenced.

<figure><picture><source srcset="/files/mVHzF449IXiEjWuZ2tEl" media="(prefers-color-scheme: dark)"><img src="/files/Msr47v2JFqUl8KPVe5Ue" alt=""></picture><figcaption></figcaption></figure>

#### [Opt-out process](/offers/guides/purchase-workflow-overview/opt-out-offer.md)

In circumstances where a customer chooses to purchase the anchor product or service, but not the offer. An opt-out request is used to notify XCover of a non-opted offer. This assists with pricing and product offer data analysis and ultimately improved offers and sales results.

<figure><picture><source srcset="/files/dwWDnv16964QwuYsNdrV" media="(prefers-color-scheme: dark)"><img src="/files/phFNCeUqu4kJvLsrWV0z" alt=""></picture><figcaption></figcaption></figure>


---

# 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://partner-docs.covergenius.com/offers/vertical-examples/property-renters.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.