XClaim API Documentation for Partners (1.4.0)

Download OpenAPI specification:Download

Introduction

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

The typical workflow would be to get claim types based on a policy type, and then ask the customer which claim type they would like to lodge. Afterwards, make a request to get he FNOL for that claim type.

Afterwards, 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.

Appendix

Featue Flags

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 repsonses for Claim Submission, examples can be seen in the claim submission responses in this documentation

Section Field Types

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

  • string

    • return a string
  • email

  • 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 lattitude 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

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

External Statuses

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

  • Claim Submitted

  • Information Processing

  • Under Assessment

  • More Information Needed

  • Approved - Pending Payment

  • Approved - Payment Sent

  • Denied

  • Invalid

  • Duplicate

  • Closed

  • Withdrawn

Authentication

httpBearer

Security Scheme Type HTTP
HTTP Authorization Scheme bearer

First Notice Of Loss

Resources related to getting a First Notice Of Loss form

Get Claim Selector

Returns a Claim Selector that can be used to determine the best claim type for a customer to submit a claim for

You can display a decision point to a user (starting with the referenced one in decisionPointId) and use the answers to show more decision points until either a claim type id or a point with no answer is reached. Use the claim type id to get the fnol for the user to submit a claim to.

Authorizations:
path Parameters
partnerCode
required
string
claimSelectorUuid
required
string
header Parameters
Content-Type
required
string
Example: application/json

Responses

200
404

Unexpected error in API call. See HTTP response body for details.

get /partners/{partnerCode}/claim-selectors/{claimSelectorUuid}
https://staging.api.xclaim.xcover.com/partners/{partnerCode}/claim-selectors/{claimSelectorUuid}

Response samples

Content type
application/json
Copy
Expand all Collapse all
{
  • "data":
    {
    }
}

Get Claim Types

Returns a list of claim types avaiable for the given policy type, and logged in user.

Use the id of the claim type you wish to make a claim for when requesting an FNOL

Authorizations:
path Parameters
partnerCode
required
string
policyTypeName
required
string
header Parameters
Content-Type
required
string
Example: application/json

Responses

200
404

Unexpected error in API call. See HTTP response body for details.

get /partners/{partnerCode}/policy-types/{policyTypeName}/claim-types
https://staging.api.xclaim.xcover.com/partners/{partnerCode}/policy-types/{policyTypeName}/claim-types

Response samples

Content type
application/json
Copy
Expand all Collapse all
{
  • "data":
    [
    ]
}

Get Fnol

Returns data required to build a form to collect data needed to submit a claim.

Each FNOL includes 1 to n sections which contain 1 to m sectionFields.

Each sectionField has a type, which you can use to build a form element and validate the data input by cutomers. Check the Appendix for the data types currently supported.

When submitting the claim, the data should match the field type, and any of the validations it contains. Check the Appendix for a list of possible validations.

Authorizations:
path Parameters
partnerCode
required
string
claimTypeUuid
required
string
header Parameters
Content-Type
required
string
Example: application/json

Responses

200
404

Unexpected error in API call. See HTTP response body for details.

get /partners/{partnerCode}/fnol/{claimTypeUuid}
https://staging.api.xclaim.xcover.com/partners/{partnerCode}/fnol/{claimTypeUuid}

Response samples

Content type
application/json
Copy
Expand all Collapse all
{
  • "data":
    {
    }
}

Claims

Create a new Claim

Create a new claim by partner user.

Authorizations:
path Parameters
partnerCode
required
string
header Parameters
x-feature-fnol--error-shape
required
string
Example: on
Request Body schema: application/json
claimTypeId
required
string
bookingReference
required
string
quoteReference
required
string
sectionFields
required
Array of objects (SectionField1)
webhooks
required
Array of objects (Webhook)
ip_address_ipv4
required
string Nullable
ip_address_ipv6
required
string Nullable

Responses

201
422

Unexpected error in API call. See HTTP response body for details.

post /partners/{partnerCode}/claims
https://staging.api.xclaim.xcover.com/partners/{partnerCode}/claims

Request samples

Content type
application/json
Copy
Expand all Collapse all
{
  • "claimTypeId": "46CFA81E-5820-44CB-AB01-637F8A8A8E2E",
  • "bookingReference": "129JJ-F3Y0Q-INS",
  • "quoteReference": "GJ275-F3ZZQ-QOT",
  • "sectionFields":
    [