# Offer Status

An Offer and individual Products within an Offer can transition between several different statuses. Below is a state diagram of these transitions and their conditions.

<figure><img src="/files/hErAj4HlR8B9GRhNU87m" alt=""><figcaption></figcaption></figure>

\
The Offer API operates with a set number of states that an Offer can rest in.\
\
**RECEIVED**: The initial creation state for an Offer. This is not a live policy and requires confirmation to proceed.\
\
**CONFIRMED**: A successful and active Booking (or confirmed Offer). This is a live, paid-for policy that may be active or expired. This may be cancellable or modifiable, and can be claimed against.

\
**CANCELLED**: A Booking or confirmed Offer that has been formally cancelled. It cannot be claimed against, or modified.\
\
**DELETED**: A rare, final state indicating the Offer or Booking record has been removed (e.g., purged for data retention).

\
**PENDING\_PAYMENT**: An Offer that has been accepted but requires final payment confirmation before transitioning to CONFIRMED. Only relevant for Offers that are confirmed using the `require_payment_confirmation` flag during a `confirm offer` request (usually followed by the `confirm booking` request) end state if confirmed will be CONFIRMED.\
\
**FAILED**: An Offer or Booking attempt that could not be completed due to a payment failure, system refusal, or technical error.\
\
**RENEWED**: A state used to depict a prior Booking that has been successfully renewed (e.g., after an annual renewal payment is confirmed).

```
OfferStatus:
    RECEIVED
    CONFIRMED
    CANCELLED
    DELETED
    PENDING_PAYMENT
    FAILED
    RENEWED 
```


---

# Agent Instructions: 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:

```
GET https://partner-docs.covergenius.com/offers/api/responses/quote-policy-status.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.