# Introduction

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: 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://docs.covergenius.com/xclaim-api-partner-docs/readme.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.