> 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/xclaim/claim-creation-workflows/appendix.md).

# Appendix

#### Feature Flags <a href="#featue-flags" id="featue-flags"></a>

We allow feature flags to be turned on/off using headers following the pattern of

* `x-feature-fnol--name`

where name is a feature. using the strings `on` or `off` to put the feature on or off.

The current available feature flags are:

* `x-feature-fnol--error-shape`

This flag is off by default, and re-shapes the error array in 422 responses for Claim Submission, examples can be seen in the claim submission responses in this documentation

#### Section Field Types <a href="#section-field-types" id="section-field-types"></a>

These are the section field types which are possible in the FNOL

* `string`
  * return a string
* `email`
  * return a string representation of a valid email (eg. "<claims@covergenius.com>")
* `date`
  * return a string representation of a date (eg. "2019-03-25")
* `datetime`
  * return a string representation of a date and time (eg. "2019-09-09 12:15:31")
* `numeric`
  * return a number
* `url`
  * return a valid url
* `boolean`
  * return true or false (JSON boolean)
* `enum`
  * return one of the options for the field (eg: "red")
* `geolocation`
  * return a JSON object with latitude and longitude properties
* `file`
  * return array of file UUIDs, obtained from the file upload endpoint
* `set`
  * return an array of selected options for the field
* `country`
  * return a ISO 3166-2 country code (eg. "AU")
* `currency`
  * return a ISO 4217 currency code (eg. "AUD")

#### Section Field Validations <a href="#section-field-validations" id="section-field-validations"></a>

These are the validations currently supported for a section field.

* `length`
  * how short/long a `string` field should be
  * options: `min`, `max`
* `numeric`
  * how low/high a `numeric` field should be
  * options `min`, `max`
* `multiselect`
  * how many items should be included in an array (used with `set` fields)
  * options `min`, `max`
* `float`
  * `numeric` field should include decimal(s)
  * no options

#### Status Categories / External Statuses <a href="#status-categories--external-statuses" id="status-categories--external-statuses"></a>

All claim statuses are grouped into a finite set of what we call "external statuses" or "status categories", that are used for easier communicating the status of a claim. The following is the list of these statuses:

* Submitted
* Under Assessment
* Action Required
* Payment Processing
* Payment Complete
* Processing
* Declined
* Settled
* Duplicate Claim
* Under Review
* Closed
* Withdrawn

Typically claims are typically considered completed when they are either in `Declined`, `Settled` or `Payment Complete` status - but in reality, it could be some othe other less common ones such as `Closed` , `Withdrawn` or `Duplicate Claim`.

Whether a claim ends up going through `Payment Complete`or `Settled` largely depends on whether it is paid online or offline.

Due to the nature of insurance claims, most claims do not truly become "closed" for a long period of time (ie. while the policy is in effect). Some of these other statuses are there to capture various edge cases.


---

# 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/xclaim/claim-creation-workflows/appendix.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.