Get started
An introduction to FNOL, Inspections & Damage Recognition services
Last updated
An introduction to FNOL, Inspections & Damage Recognition services
Last updated
The service consists of 4 standalone services:
Item | Link | Description |
Profiles | Auth service & customer's data | |
FNOL | API to create a claim profile | |
Vehicle Inspections | API to link a bunch of photos to a claim | |
Photo processing & Damage recognition | API to process bunch of photos and detect damages |
There are several main objects in the process:
Object | Description |
DeviceToken | Device token that is used in Telematics SDK or can be received via User management API. https://docs.telematicssdk.com/platform-features/back-end-as-a-service |
Token | Authorization Token that can be received via Auth Service. |
CarToken | Car service has to be used to create a vehicle and/or get vehicle details, including Make, Model and other fields. https://docs.telematicssdk.com/platform-features/car-service |
Claim_ID | Claim ID will be provided when a claim is created. |
Screen_ID | This is a bunch of photos (vehicle photos). |
Quote_ID | This is a system object that confirms that we've received a screen for processing and damage recognition and it is currently in processing. |
Damage_ID | This is a bunch of processed photos with recognised damages. |
Note: FNOL, Inspections and Damage Recognition services are closely integrated with Vehicle management Service. You have to create a vehicle first to register a claim.
Authorize in Service. You need a user "deviceToken". Get it via registration, refresh or via search.
Create a claim. You need a vehicleToken, Make and model. A new claim with a Draft status will be created. You need to save "claim_id".
Create a screen (a bunch of images). You need a "claim_id". You can create only one screen per each claim. You need to save "screen_id".
Change claim status according to the Statuses workflow scheme.
In Draft, Processing and Pending statuses you can update the claim.
In Draft, Processing and Pending statuses you can update the screen. Validations: Screen attribute CanEdit == true.
Create quote. You need a "screen_id". Validations: Claim state == 'approved' Screen attribute CanQuotation == 'true'
Wait for Damage Report processing (quote_processing state set up automatically). When Damage Report is created (after 30-60sec), the claim will get state Executed and you can get Damage Report. You need "claim_id" and "screen_id".
All new claims are created by customers with a DRAFT status.
When your manager starts to work with a new claim, he can transfer the claim to PROCESSING status.
If there is not enough details from a customer, a PENDING status can be used.
HOLD and REJECTED statuses can be used by your manager if the claim is not allowed for further process.
If the claim is appropriate for further damage recognition process, status APPROVED can be used.
In QUOTE status the photos processing for automatic damage recognition starts.
When the damage recognition process finishes, status EXECUTED is used.
To proceed with photo processing it is required to provide at least one photo from a mandatory type of photo. The full list of screens and guide are available here: https://docs.telematicssdk.com/platform-features/fnol-inspections-and-damage-recognition/screens/vehicle-photos-dictionary
Type of photo | Flag |
| Mandatory. At least one photo must be provided. |
| Not mandatory. |
