> 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/testing-and-go-live.md).

# Testing & go-live

Test your Offers API integration, run it alongside RentalCover, and switch traffic over safely.

## Test environment

There is no separate staging URL. You test against the **production base URL with test credentials**. Test policies are not live cover. See [Testing API Keys](https://partner-docs.covergenius.com/offers/api/authentication.md#testing-api-keys).

You build against a **reference configuration** that mirrors the standard RentalCover product set. It is not your production configuration, so expect products and prices to change when your own configuration goes live.

## Test scenarios

| Scenario                   | What to verify                                                                                                                          |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| Each product you sell      | The offer returns the expected products, prices and document links for each market                                                      |
| Offer, then Confirm        | The booking ID is an INS (`XXXXX-XXXXX-INS`), status is `CONFIRMED`, and `total_price` matches what you showed                          |
| Opt-out                    | The call returns `204` with no body                                                                                                     |
| Pending, then finalise     | Confirm with `require_payment_confirmation` returns `PENDING_PAYMENT`. Finalising moves it to `CONFIRMED`                               |
| Cancel preview and confirm | The preview returns `refund_value`, `total_refund`, `cancellation_id` and `confirm_before`. Confirming moves the booking to `CANCELLED` |
| One-step cancel            | The booking is cancelled and the refund fields are what you expect                                                                      |
| Rebooking                  | Cancel, then Create Offer with the rebooking fields, then Confirm. The new INS is stored and linked to the old one                      |
| Customer details change    | Details change, the INS stays the same, and arrays you send are replaced in full                                                        |
| Price-affecting change     | Quote for update returns the new price and an `update_id`. Confirm update applies it to the same booking                                |
| Webhooks                   | Your listener verifies the signature, returns `200` and handles a repeated event                                                        |
| v2 errors                  | Your code reads `code`, `errors[]` and `metadata.field_errors`, and logs `error_id`                                                     |
| Idempotent replay          | Repeating Confirm or Cancel with the same key returns `409`, and your code treats it as success                                         |
| Residency mismatch         | Confirm with a `policyholder.country` different from `customer.country` is rejected                                                     |
| Expired offer              | Confirm after the validity window returns `404`, and you request a new offer                                                            |
| Get Booking                | Returns the expected status, quotes and documents for confirmed, pending and cancelled bookings                                         |
| List Bookings              | `status=CONFIRMED` and `status=CANCELLED` with a date range return the bookings you expect, and paging with `next` reaches the end      |

When these pass, walk through them with your CSE to sign off the integration.

## Run both APIs in parallel

You can switch traffic in stages, for example one market or channel at a time.

{% hint style="warning" %}
**Parallel run rules**

* **Quote and confirm on the same API.** An offer created on the Offers API can't be purchased on RentalCover, and the other way round.
* **Bookings stay where they were issued.** Cancel, update and check RentalCover bookings on RentalCover until their cover ends, and Offers bookings on the Offers API.
* **Record which API issued each booking**, so every later call goes to the right place.
* **Rolling back** means routing new quotes back to RentalCover. Bookings already issued on the Offers API stay there.
  {% endhint %}

During the parallel run, monitor:

* Success rates compared with RentalCover
* `4xx` and `5xx` responses by endpoint
* Differences between the price shown and the Confirm `total_price`
* Webhook failures and cancellations you can't match
* Bookings stuck in `PENDING_PAYMENT`

## Go-live checklist

* [ ] Production credentials are stored on the server, one pair per environment.
* [ ] Request signing works with a correct `Date` header, and server clocks are in sync.
* [ ] Booking ID validation accepts the INS format with five characters in each group.
* [ ] `x-idempotency-key` is sent on every call that needs one.
* [ ] Offer, Confirm, Opt-out and pending confirmation work for every product and market in scope.
* [ ] The residency sent at Create Offer matches `policyholder.country` at Confirm.
* [ ] Cancellation, rebooking and modification work, and `fields_allowed_to_update` controls what you let customers edit.
* [ ] The webhook listener is live, verifies signatures, returns `200` and is idempotent.
* [ ] Document links, `account_url` and `fnol_link` come from the API responses.
* [ ] Every request sends `X-API-Error-Version: v2`, and errors are logged with their `error_id`.
* [ ] Monitoring, alerting and the `5xx` retry policy are in place.
* [ ] Your records show which API issued each booking.
* [ ] The Cover Genius verification checklist is signed off.
* [ ] The rollback route is agreed.

## See also

* [Integration Checklist](https://partner-docs.covergenius.com/offers/guides/integration-checklist.md)
* [Authentication](https://partner-docs.covergenius.com/offers/api/authentication.md)


---

# 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/testing-and-go-live.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.
