> 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-elements/api-integration/summary.md).

# Summary

XCover Elements handles the front-end presentation of offers to your customers. When a customer views protection products, XCover Elements creates offers automatically — no backend integration is needed for this step.

Once a customer has selected or declined a protection product, your backend server integrates directly with the **XCover API** to complete the transaction. This includes:

* **Confirming an offer** the customer has accepted
* **Opting out** of an offer the customer has declined

**Connecting frontend to backend:** The offer response from XCover Elements contains a `provider_reference` field. Use the IDs from `provider_reference` when making requests to the XCover API — these map the frontend offer to the corresponding XCover resource.

**Authentication:** The XCover API uses HMAC signature authentication for all server-to-server requests.

{% hint style="info" %}
More on Confirm Offer and Opt out API specs: [XCover API Reference](https://partner-docs.covergenius.com/xcover/api/reference)
{% endhint %}

You can use the HTML Demo under Client Integration Examples to display an example frontend widget, and the [Postman Collection](https://web.postman.co/workspace/%5BGitBook%5D-XCover-Elements-Demo~4aca8c38-22e6-4762-8cc7-0be5c3ed0ec7/collection/9582676-47676b6b-2078-40ce-82c7-7f269d1c2020) for the same demo partner to see example booking requests against the XCover API.

{% hint style="warning" %}
**Note: The Postman collection requires access. Please liase with your key account manager to request access.**
{% 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 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/xcover-elements/api-integration/summary.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.