Claims Management
To initiate a claim using the Shield API, the user creating the claim must first be registered. For security reasons, we recommend using the OTP (one-time password) creation and confirmation endpoint sent to the user's email to confirm ownership of the email address used for the claim. Once verified, follow this workflow: retrieve the user’s active risk items, which include items where they are the authorized claimant. Present these items to the user for selection. Upon selection, you can use the risk item UID to retrieve the available variants. With the claimant, risk item, and variant details established, a claim can be created, tying together the claimant, the risk item, and the contested variant. A claim allows you to explain what happened to a single risk item with regard to a specific variant, which has its own rules and exceptions. During the claim process, the user might be asked to provide additional information to corroborate their claim; this information is archivable using the communication endpoints.
Endpoints
GET
GET
GET
GET
POST
GET
GET
GET
POST
POST
GET
Step-by-Step Workflow
To initiate a claim using the Shield API, the user creating the claim must first be registered. For security reasons, this is accomplished via an OTP (One-Time Password) confirmation code sent to the user’s email to confirm that they are the owner of the email submitting the claim.
Once verified, the workflow is as follows: retrieve the user’s active risk items, which include items where they are either the holder or an authorized claimant. Present these items to the user for selection. Upon selection, you can now use the risk item UID to retrieve the available coverages by identifying the correct variant. With the claimant, risk item, and coverage details established, a claim can then be created, tying together the claimant, the risk item, the contested coverage, and the relevant policy. A claim allows you to explain what happened to a single risk item in regards to a specific coverage, which has its own rules and exceptions. During the claim process, the user might be asked to provide additional information to corroborate their claim.
Identify the user
You can identify the user using its uid or id.
GET
https://api.insurehero.io/api/shield/v1/users/:userId
Headers
Authorization*
string
Bearer access token
Path Parameters
userId*
string
Either user_id or uid
Query Parameters
searchBy
id | uid
Field use to search for a matching user. Default to 'id'
Or using its email.
GET
https://api.insurehero.io/api/shield/v1/users/by-email/:userEmail
Path Parameters
userEmail*
string
The user email
Example Response
Get the user's risk items
After retrieving user information, you can access all risk items associated with them. It's important to note that this association relies on the 'authorized_claimants' array within the risk items. Each object inside this array must include the 'email' key with the user's email address, which should be registered using the user post route. These email addresses must correspond to existing entries in the user table for the association to be valid.
GET
https://api.insurehero.io/api/shield/v1/users/:userId/risk-items
Headers
Authorization*
string
Bearer access token
Path Parameters
userId*
string
Either user_id or uid
Query Parameters
searchBy
id | uid
Field use to search for a matching user. Default to 'id'
Example Response
Get the variants available for the risk item
You can get all the variants available that cover a Risk Item
GET
https://api.insurehero.io/api/shield/v1/risk-items/:riskItemId/variants
Headers
Authorization*
string
Bearer access token
Path Parameters
riskItemId*
string
The risk item ID
Example Response
Create a Claim
Once you have all the information you can create the claim.
Good to know
It's very likely that the UID of the variants might not be descriptive enough or could even be confusing (imagine a variant named "life_insurance_up_to_1,000"). Therefore, we recommend displaying the variant's description and/or name when selecting it, while sending us the variant UID in the background.
Create a new claim for a risk item
POST
https://app.insurehero.io/api/shield/v1/claims
Headers
Authorization*
string
Bearer access token
User-Authorization*
string
Request Body
risk_item_id*
string
Item being claimed
variant_id*
string
The coverage variant chosen for this claim
metadata
object
Additional data of this claim
subject*
string
A sentence describing the claim
incident*
IncidentType
Incident data
claim_amount
number
A positive number requested to be paid
Types of responses
Example Response 201
IncidentType
date*
date
summary
string
details*
DetailsType
adittional_properties*
JSON
DetailsType
transaction*
TransactionType
description
string
TransactionType
date
string
amount
number
method
VISA, MASTERCARD, AMEX, DISCOVER o TRANSFER
retailer
string
description
string
User claims
Fetch all claims from a given user
GET
https://api.insurehero.io/api/shield/v1/users/:userId/claims
Path Parameters
userId*
string
Either user_id or uid
Query Parameters
searchBy
id | uid
Field use to search for a matching user. Default to 'id'
Headers
Authorization*
string
Bearer access token
All claims
GET
https://app.insurehero.io/api/shield/v1/claims
A paginated list of all claims.
Page size cannot exceed 100 records at a time.
Headers
Authorization*
string
Bearer access token
Query Parameters
from*
string
Starting record index
to*
string
Ending record index
comm_info
boolean
Communication information for that claim
policy_ref
boolean
The policy detail for that claim
general
boolean
The details of the claim
Types of responses
Example Response 200
Get the data of a given claim
GET
https://app.insurehero.io/api/shield/v1/claims/:claimId
Headers
Authorization*
string
Bearer access token
Path Parameters
claimId*
string
Claim identifier
Query Params
comm_info
boolean
Communication information for that claim
policy_ref
boolean
The policy detail for that claim
general
boolean
The details of the claim
Types of responses
Example Response 200
Additional resources
Add Event to Claim
Add a new event with asynchronous data to a claim
POST
https://app.insurehero.io/api/shield/v1/claims/:claimId/events
Headers
Authorization*
string
Bearer access token
Path Parameters
ClaimId*
string
Claim identifier
Request Body
event_data*
object
Additional data related to an event. "start_date" and "end_date" are obligatory
metadata
object
Additional data to include in the event
Example response
Get Claim events
GET
https://app.insurehero.io/api/shield/v1/claims/:claimId/events
Events in a claim
Headers
Authorization*
string
Bearer access token
Path Parameters
ClaimId*
string
The id of the claim associated with the events
Example response
Post a Claim without User-Authorization token
To create a claim without User-Authorization token, you will need to contact our support team. Once you have requested authorization and it has been granted, you will be provided with the specific instructions to carry out this action.
You can still use the method of sending the token and not sending the claimant_email even if your channel has permissions.
POST
https://app.insurehero.io/api/shield/v1/claims
Headers
Authorization*
string
Bearer access token
Request Body
risk_item_id*
string
Item being claimed
claimant_email*
string
Claimant email
variant_id*
string
The coverage variant chosen for this claim
metadata
object
Additional data of this claim
subject*
string
A sentence describing the claim
incident*
IncidentType
Incident data
claim_amount
number
A positive number requested to be paid
Types of responses
Example Response 201
IncidentType
date*
date
summary
string
details*
DetailsType
adittional_properties*
JSON
DetailsType
transaction*
TransactionType
description
string
TransactionType
date
string
amount
number
method
VISA, MASTERCARD, AMEX, DISCOVER o TRANSFER
retailer
string
description
string
Last updated