> 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/guides/migrating-from-rentalcover.md).

# Migrating from RentalCover

Move an existing RentalCover API integration to the XCover Offers API. What changes, what stays the same, and the steps to migrate.

The RentalCover API is being retired, and every partner needs to move to the XCover Offers API (Dynamic Offers). New capabilities ship on the Offers API only. Your Cover Genius Client Solutions Engineer (CSE) will confirm the retirement date and help you plan the work into your roadmap.

It's an upgrade, not a rebuild. Quote becomes **Create Offer** and Purchase becomes **Confirm Offer**. A standard integration typically takes three to four weeks end to end, including testing.

You can migrate incrementally. Both APIs run side by side, so you can move traffic market by market or channel by channel, and bookings you already issued on RentalCover stay there until their cover ends.

## Why migrate

* **More products without more builds.** Offer travel disruption, weather protection, comprehensive travel, medical, Cancel For Any Reason, baggage and gadget protection, and eSIMs alongside Full Protection, Extra Cover and CDW. Products, tiers and bundles are configuration on the Cover Genius side, not code you ship. Availability varies by market.
* **Your own experiments.** Test products and pricing from the Partner Portal and roll out what works without an engineering release.
* **Real-time data in the Partner Portal.** Sales, claims and support performance, booking management, reports and invoices. The booking data behind these views doesn't flow through the RentalCover API.
* **New features ship on the Offers API only.** New products, pricing capabilities and API features are being rolled out to the Offers API. The RentalCover API won't receive them.
* **A better developer experience.** One signed credential for every XCover product, consistent JSON with numeric amounts and dates that carry their time-zone offset, safe retries with idempotency keys, machine-readable error codes, signed webhooks and a full OpenAPI reference.

{% hint style="info" %}
**What your developers get**

* **One signed credential** for every XCover product.
* **In-place modification**: change dates or customer details without cancelling and rebooking.
* **Cancellation preview**: show the refund before the customer agrees to cancel.
* **Signed webhooks** for cancellations and updates made outside your platform.
* **Structured errors and idempotent writes**, so retries are safe.
  {% endhint %}

## Migration steps

1. [Set up credentials, request signing and error handling](https://partner-docs.covergenius.com/offers/guides/migrating-from-rentalcover/authentication-and-errors.md)
2. [Migrate your purchase flow](https://partner-docs.covergenius.com/offers/guides/migrating-from-rentalcover/purchase-flow.md): Quote and Purchase become Create Offer and Confirm.
3. [Migrate cancellations](https://partner-docs.covergenius.com/offers/guides/migrating-from-rentalcover/cancellation.md): add an optional refund preview.
4. [Migrate modifications](https://partner-docs.covergenius.com/offers/guides/migrating-from-rentalcover/modification.md): update bookings in place.
5. [Track bookings](https://partner-docs.covergenius.com/offers/guides/migrating-from-rentalcover/track-bookings.md): replace status and list calls with Get Booking and List Bookings, and subscribe to webhooks.
6. [Test, run in parallel and go live](https://partner-docs.covergenius.com/offers/guides/migrating-from-rentalcover/testing-and-go-live.md)

Before you build, agree the following with your Cover Genius Client Solutions Engineer (CSE): products and markets, pricing model, payment model, cancellation window, modification channels and offer validity window.

## What changes

| Area               | Before: RentalCover                                             | After: XCover Offers                                                                                                                         |
| ------------------ | --------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| Authentication     | Static `X_API_KEY` header                                       | Signed `Authorization` and `Date` headers, one key and secret for all XCover products                                                        |
| Request shape      | Flat PascalCase payload                                         | Nested `customer`, `partner` and `context` objects in snake\_case                                                                            |
| Personal data      | Sent at Quote                                                   | Sent at Confirm only. Create Offer carries no personal data                                                                                  |
| Product selection  | `Type` field                                                    | `context.product` plus rental context. Cover Genius decides the product mix                                                                  |
| Booking ID (INS)   | Two groups of 4 characters: `XXXX-XXXX-INS`. Returned at Quote  | Two groups of 5 characters: `XXXXX-XXXXX-INS`, with an optional region prefix such as `U-`. Returned at Confirm. Offers and quotes use UUIDs |
| Modification       | `updateCustomer`; trip changes mean cancel and rebook           | Updated in place. The INS does not change                                                                                                    |
| Cancellation       | One call                                                        | Optional preview, then confirm. Or one call                                                                                                  |
| Notifications      | Cancellation notification, where configured                     | Signed `BOOKING_CANCELLED` (required) and `BOOKING_UPDATED` (optional) webhooks                                                              |
| Money and dates    | Amounts as strings. `yyyy-mm-dd hh:mm:ss`, no offset            | Amounts as numbers. RFC 3339 with the local offset                                                                                           |
| Errors             | HTTP 400 with an `errors` key                                   | HTTP 422. Optional v2 format with a machine-readable `code` on offer endpoints                                                               |
| Lists and invoices | `getAllPurchasedPolicies`, `getAllCancelledPolicies`, `invoice` | List Bookings, filtered by `status` and date. Invoices are in the Partner Portal                                                             |

## What stays the same

* The products you sell today, and their pricing at launch.
* Your cancellation window, configured to match your current terms.
* Your payment model: single, dual or mixed. Dual payment now uses an XPay token instead of card details.
* One insured person per policy.
* Cover Genius sends the customer emails and documents.

{% hint style="warning" %}
**The booking ID format changes.** The INS grows from two groups of **4** uppercase letters and digits to two groups of **5**: `XXXX-XXXX-INS` becomes `XXXXX-XXXXX-INS`. Update any validation, regular expressions and fixed-length database columns before go-live. During the parallel run you need to accept both formats.

Bookings issued from some regional deployments start with a one-letter region prefix, for example `U-XXXXX-XXXXX-INS` (United States) or `I-XXXXX-XXXXX-INS` (India). Allow for the optional prefix in your validation.
{% endhint %}

{% hint style="warning" %}
Bookings issued on the RentalCover API stay on the RentalCover API for their whole lifecycle. Keep your RentalCover calls for cancelling, updating and checking them until their cover ends.
{% endhint %}

## Endpoint map

Offers API paths are relative to `https://api.xcover.com/x/partners/{partner_code}`. Use them exactly as written: some paths end in a slash and some don't, and the wrong form returns `404`.

| RentalCover                                                                                | XCover Offers                                                                                                               | Guide                                                                                                             |
| ------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| `POST /insurances/quote`                                                                   | `POST /offers/`                                                                                                             | [Purchase flow](https://partner-docs.covergenius.com/offers/guides/migrating-from-rentalcover/purchase-flow.md)   |
| `POST /insurances/purchase`                                                                | `POST /offers/{offer_id}/confirm/`                                                                                          | [Purchase flow](https://partner-docs.covergenius.com/offers/guides/migrating-from-rentalcover/purchase-flow.md)   |
| —                                                                                          | `PUT /bookings/{booking_id}/confirm` (finalise a pending booking)                                                           | [Purchase flow](https://partner-docs.covergenius.com/offers/guides/migrating-from-rentalcover/purchase-flow.md)   |
| `POST /insurances/coverOptOut/{reference}`                                                 | `POST /offers/{offer_id}/opt_out/`                                                                                          | [Purchase flow](https://partner-docs.covergenius.com/offers/guides/migrating-from-rentalcover/purchase-flow.md)   |
| `POST /insurances/cancel/{reference}`                                                      | `POST /bookings/{booking_id}/cancel`, optionally then `POST /bookings/{booking_id}/confirm_cancellation/{cancellation_id}/` | [Cancellation](https://partner-docs.covergenius.com/offers/guides/migrating-from-rentalcover/cancellation.md)     |
| `POST /insurances/updateCustomer`                                                          | `PATCH /bookings/{booking_id}/`                                                                                             | [Modification](https://partner-docs.covergenius.com/offers/guides/migrating-from-rentalcover/modification.md)     |
| `POST /insurances/update/{reference}`                                                      | `PATCH /bookings/{booking_id}/quote_for_update`, then `POST /bookings/{booking_id}/confirm_update/{update_id}/`             | [Modification](https://partner-docs.covergenius.com/offers/guides/migrating-from-rentalcover/modification.md)     |
| `GET /insurances/status/{reference}`                                                       | `GET /bookings/{booking_id}`                                                                                                | [Track bookings](https://partner-docs.covergenius.com/offers/guides/migrating-from-rentalcover/track-bookings.md) |
| `POST /insurances/getAllPurchasedPolicies`                                                 | `GET /bookings/?status=CONFIRMED`, with optional date and customer filters                                                  | [Track bookings](https://partner-docs.covergenius.com/offers/guides/migrating-from-rentalcover/track-bookings.md) |
| `POST /insurances/getAllCancelledPolicies`                                                 | `GET /bookings/?status=CANCELLED`, with optional date and customer filters                                                  | [Track bookings](https://partner-docs.covergenius.com/offers/guides/migrating-from-rentalcover/track-bookings.md) |
| `GET /insurances/invoice/{reference}`                                                      | No endpoint. Invoices are in the Partner Portal                                                                             | [Track bookings](https://partner-docs.covergenius.com/offers/guides/migrating-from-rentalcover/track-bookings.md) |
| Cancellation notification, `GET /notifications/list`, `POST /notifications/update/{event}` | `BOOKING_CANCELLED` and `BOOKING_UPDATED` webhooks. Nothing to poll or acknowledge                                          | [Track bookings](https://partner-docs.covergenius.com/offers/guides/migrating-from-rentalcover/track-bookings.md) |

`{booking_id}` is the INS returned by Confirm.

## Next

{% content-ref url="/pages/z2IBqkf9ojmW6TaaSk9d" %}
[Credentials, signing & errors](https://partner-docs.covergenius.com/offers/guides/migrating-from-rentalcover/authentication-and-errors.md)
{% endcontent-ref %}


---

# 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/offers/guides/migrating-from-rentalcover.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.
