> 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/readme.md).

# Introduction

This document describes the API resources in the XClaim product, available for Cover Genius partners to use within it's ecosystem.

These are the API endpoints that may be required for integration.

Afterward, you would orchestrate the collection of data from the customer for that claim type (based on the fields required - as returned by the FNOL), and when ready, create a new claim with that data. Any files should be uploaded beforehand, and their UUIDs used as the values of the respective FNOL data fields.

### API Overview

This is a JSON REST API, which aims to be compatible with the `JSON:API` specification.

When making API requests, please use `application/json` in the `Content-Type` header.

In terms of authentication, you should obtain a JWT, as described in the Authentication page. You should use it in the `Authorization` header like so;

<pre><code><strong>Bearer &#x3C;TOKEN>
</strong></code></pre>

#### Internationalization <a href="#internationalization" id="internationalization"></a>

XClaim supports seamless translations for all content that is customer-facing. However, not all content is translated (and not to every language) by default - it depends on your specific use cases. This is something to discuss with the partnerships team.

If you are in a situation where you are supporting multiple languages, you can ensure that XClaim returns translated content, by using the `Accept-Language` header. The specific locales supported, depend on your integration.

Some examples;

* `Accept-Language: zh-hans`
* `Accept-Language: zh-hant_tw`
* `Accept-Language: ru`
* `Accept-Language: pt-br`

The default locale for our platform is `en`.

#### Dates & Timestamps <a href="#internationalization" id="internationalization"></a>

When parsing timestamps, ours will be output in an ISO 8601 format, so if you are parsing any timestamp, be sure your parser supports the full standard. For example, a timestamp may be `2025-02-26T09:31:27Z` , `` 2025-02-26T09:31:27.00000Z` ``or `2025-02-25T21:31:27−12:00`as well as others described in the ISO standard.


---

# 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/xclaim/readme.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.