> 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/rentalcover/shared-reference/booking-statuses-and-errors.md). # Booking Statuses & Errors ## Booking Statuses

Status	Meaning
`Received`	Quote created; payment has not yet been taken.
`PendingConfirm`	Payment has been taken; final confirmation from the insurer is pending.
`Confirmed`	Protection is active and confirmed by the insurer.
`Cancelled`	Protection has been cancelled.

## Errors The RentalCover API uses standard HTTP status codes. When a request fails, the response body contains a JSON object describing the error. ### **HTTP status codes**

Code	Meaning	What to do
`200`	Success	The request completed successfully.
`400`	Bad request	A required parameter is missing, invalid, or the request conflicts with the current booking state. Read the error message in the response body.
`401`	Unauthorised	Your API key is missing or invalid. Check the `X_API_KEY` header.
`404`	Not found	The endpoint or resource does not exist. Check the URL and booking reference.
`500`	Internal server error	An unexpected error occurred on the RentalCover server. Contact your CSE if this persists.

### Error response body ```json // Single-field validation error { "errors": { "email": ["Email cannot be blank."] } } // General request error { "errors": ["Policy cannot be purchased or modified after the date of travel"] } ``` ### Common error scenarios General errors typically return `HTTP 400`. #### Quote errors

Scenario	Example error
Required field missing	"Email cannot be blank." / "FromDate: must be in the future"
Invalid country code	"Country is too long (maximum is 2 characters)."
Invalid language code	"Language Code is too long (maximum is 5 characters)."
SIPP code not covered by underwriters	"No policies available for SIPP code."
Region without trading licence	"No policies are available for the requested state, province or territory."

#### Purchase errors

Scenario	Example error
Booking details differ from quote	"Policy not found"
Purchase attempted after travel date	"Policy cannot be purchased or modified after the date of travel"
Booking not found	"Booking details not found"
Payment failure	"Payment validation failed, please make sure your credit card details are correct or try another card"
Invalid or expired coupon	"Invalid or expired coupon, please try again or remove coupon"

#### Cancel errors

Scenario	Example error
Invalid booking reference	"Booking not found"
Already cancelled	"Booking AB12-345C-INS can not be cancelled, already been cancelled on 2024-01-23"
Claim in progress	"Booking 98PD-SEQN-INS can not be cancelled, claim in progress"
Charge dispute raised	"Booking F8TU-62C6-INS can not be cancelled as it has been disputed"

For further troubleshooting, please contact your CSE. --- # 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/rentalcover/shared-reference/booking-statuses-and-errors.md?ask=&goal= ``` `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.