Telematics SDK | Developer portal
  • Get started
  • 4 Steps to Integrate SDK
  • Product Wiki
  • License
  • FAQ
  • PRODUCT DESCRIPTION
    • How it works
    • SDK Features
    • Scoring
      • Risk driving Scoring
        • Event detection
        • Trip rating
        • Overall scoring
      • Eco Scoring
    • Dataset
      • Dataset | User statistics API
      • Data samples
        • Summary - Processed track details (Rich track details)
        • Processed track waypoints (Rich track points)
        • Summary - list of Processed tracks
        • Incoming track events
        • Incoming track points (waypoints)
        • Summary - list of Incoming tracks
      • Dataset Decription
        • Bluetooth OBD - Vehicle Dataset
        • LastKnownPoints
        • IncomingTrackPoints
        • IncomingTrackEvents
        • Enriched telematics data
          • RichTracks
          • RichTrackPoints
          • RichTrackEvents
          • RichTrackDetails
          • UserStatisticDrivingDetails
        • Raw telematics data from SDK
    • Reporting
      • Drivecoins summary
      • Trip summary
      • Scoring summary
      • User state
      • Fraud
      • Trip waypoints
      • Trip events
    • External Articles
      • Why mobile telematics hits hardware telematics
  • Step 1: Create Datahub Account
  • Step 2: SDK Installation
    • Get started
    • iOS SDK installation
      • *Set up Your Development Environment
      • *Configure Your Project
      • *App Delegate
      • *Configure Framework
      • *React Native Installation
        • Create the iOS bridge
      • Add list of trips to your ViewController
      • Add statistics data to your ViewController
      • *What’s different in iOS 13?
      • *iOS 13 Permissions Wizard
      • *SDK Enable \ Disable \ Disable With Upload
      • *Incoming Tags
      • *Tracking Status
      • *SDK Delegates
      • *SDK Modes
      • *Using the Debugging Tools in Simulator
    • Android SDK installation
      • *Getting started
        • *Set up Your Development Environment
        • *Setup and enable SDK
        • *Permissions wizard
        • *Permissions dialog
        • *Configure SDK variables for notifications
      • *Subscribe to tracking events
      • *Incoming tags managing
      • *Migration from SDK v1.6.x to SDK v2.0.x
    • *Check SDK Installation
      • iOS Simulator
      • DataTool
      • ZenRoad
    • *Demo Applications
      • iOS | Open Source Demo Application
      • iOS | SDK Demo Application
      • iOS | Swift | SDK Demo Application
      • Android | SDK Demo Application
      • Android | Java | SDK Demo Application
      • Flutter | SDK Demo Application
    • SDK Changelog
      • Android SDK Changelog
      • iOS SDK Changelog
    • Permissions Guides
      • First Launch
        • iOS 13 (and higher) Permissions Guide
        • iOS 12 (and lower) Permissions Guide
        • Android 9 Permissions Guide
        • Android 9 XIaomi Permissions Guide
        • Android 10 Permissions Guide
      • *Troubleshooting
        • iOS — Troubleshooting
          • iOS — Troubleshooting
        • Android — Troubleshooting
          • Samsung — Troubleshooting
          • Oppo — Troubleshooting
          • Huawei — Troubleshooting
          • Xiaomi — Troubleshotting
          • OnePlus — Troubleshooting
          • Meizu — Troubleshooting
          • Asus — Troubleshooting
          • Vivo — Troubleshooting
          • Wiko — Troubleshooting
  • Step 3: Register SDK users
    • User Registration (API)
  • Step 4: API | User Statistics, Scores, Trips
    • Step 4: Get Statistics, Scorings and Trip Data
    • API Authorization
    • Statistics and Scoring APIs
      • Get started - Statistics and Scoring API
      • User | Individual Scorings and Statistics
      • Admin | User(s) - Scorings and Statistics
      • Admin | Consolidated Scorings and Statistics
    • Trips API
      • Get a short list of tracks
      • Get a list of tracks with paging
      • Get a list of tracks by IDs
      • Get a single track with waypoints
      • Get the most earliest track
      • Track Statuses
  • SDK Features
    • *Bluetooth Device - Get started
      • *Get Started
      • *Android - ELM API
      • *iOS - ELM API
    • Trip Tags - Get started
      • Tags for trips via mobile app
        • Android - Tags for trips
        • iOS - Tags for trips
      • Tags for period
      • Trip log by tags
  • PLATFORM FEATURES
    • *User Management
      • *User Registration
      • *Check User Existence
      • *User Management
    • *Vehicle Management
      • *Directories
      • *Vehicles
    • FNOL, Inspections & Damage Recognition
      • Get started
      • Profiles
      • Claims
      • Vehicle inspections
        • Dictionary of vehicle photos
      • Photo processing
    • *Leaderboard
      • *Summary Leaderboard
      • *Leaderboard by factors
      • Swagger - Leaderboard
    • *Streaks
    • *SNS
      • *How to register AWS SNS
    • 3rd party data processing
      • Swagger - Incoming getaway
    • *User & Permissions Status | Heartbeats
  • Other
    • Response Codes
    • Resources swaggers
      • Swagger: User service
      • Swagger: Scorings and Statistics API
      • Swagger: Telematics data
      • Swagger: Leaderboard
      • Swagger: Vehicle Management
      • Driving details
      • Swagger: FNOL, Inspections & Damage Recognition
      • Swagger: Heartbeats
    • Archive
      • Get started
      • Statistics and Scorings API
      • Step 5: Get statistics and trip data [ARCHIVED]
      • User Statistics API [Archived]
      • SDK - Statistics API [ARCHIVED]
        • Get the data to the Android app
          • Android Telematics data (Tracks)
            • Check current running track state
            • Get start date for current recording trip
            • Register tracking state listener (for onStartTracking/onStopTracking events)
            • Register speed violations listener
            • Get flag for registered speed violations listener
            • Get registered speed limit in km/h or default
            • Get registered speed violations timeout in ms or default
            • Get Tracks
            • Get detailed trips information
            • Get available user roles
            • Change a user role (any of TrackOriginDictionary.code)
          • Android User Statistics
            • Get Dashboard info
            • Get detailed Dashboard
            • Get Driving time statistics
            • Get Speeding statistics
            • Get Mileage statistics
            • Get Distracted Phone Usage statistics
        • Get the data to the iOS app
          • Other methods
          • iOS Telematics data (tracks)
            • Request all Tracks with specified offset and limit
            • Request all Tracks with specified offset and limit. No filter will be used in request
            • Request Track info with specified Track Token
            • Request Track origins dictionary
            • Change Track Origin Code
            • Share Track
          • iOS User Statistics
            • Get shared Track
            • Request main statistics data for all possible statistic types
            • NS_ENUM
            • Request main statistics data for all possible statistic types
            • Properties and Protocols
      • Get all DeviceTokens
    • Report a bug
    • Data Hub
    • Talk to sales
  • Postman collection
Powered by GitBook
On this page
  • Dependencies
  • API Usage Scenario
  • Overall workflow and statuses (states)
  • Statuses
  • Case study - Zenroad app
  • Photo processing

Was this helpful?

  1. PLATFORM FEATURES
  2. FNOL, Inspections & Damage Recognition

Get started

An introduction to FNOL, Inspections & Damage Recognition services

PreviousFNOL, Inspections & Damage RecognitionNextProfiles

Last updated 4 years ago

Was this helpful?

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

Dependencies

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.

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.

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.

API Usage Scenario

Overall workflow and statuses (states)

Statuses

  1. All new claims are created by customers with a DRAFT status.

  2. When your manager starts to work with a new claim, he can transfer the claim to PROCESSING status.

  3. If there is not enough details from a customer, a PENDING status can be used.

  4. HOLD and REJECTED statuses can be used by your manager if the claim is not allowed for further process.

  5. If the claim is appropriate for further damage recognition process, status APPROVED can be used.

  6. In QUOTE status the photos processing for automatic damage recognition starts.

  7. When the damage recognition process finishes, status EXECUTED is used.

FNOL

Vehicle inspection

Photo processing and damage recognition

Photo processing

Type of photo

Flag

  • Front

  • Back

  • Left front wing

  • Left front door

  • Left rear door

  • Left rear wing

  • Right rear wing

  • Right rear door

  • Right front door

  • Right front wing

Mandatory. At least one photo must be provided.

  • Front left diagonal

  • Front right diagonal

  • Back left diagonal

  • Back right diagonal

  • Left

  • Right

  • Windshield

  • Dashboard

Not mandatory.

Note: FNOL, Inspections and Damage Recognition services are closely integrated with . You have to create a vehicle first to register a claim.

in Service. You need a user "deviceToken". Get it via , or via .

. You need a . A new claim with a Draft status will be created. You need to save "claim_id".

(a bunch of images). You need a "claim_id". You can create only one screen per each claim. You need to save "screen_id".

according to the .

In Draft, Processing and Pending statuses you can .

In Draft, Processing and Pending statuses you can . Validations: Screen attribute CanEdit == true.

. 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 . You need "claim_id" and "screen_id".

Case study -

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:

Vehicle management Service
Authorize
registration
refresh
search
Create a claim
vehicleToken, Make and model
Create a screen
Change claim status
Statuses workflow scheme
update the claim
update the screen
Create quote
get Damage Report
Zenroad app
https://docs.telematicssdk.com/platform-features/fnol-inspections-and-damage-recognition/screens/vehicle-photos-dictionary
Profiles
Claims
Screens
Quotes
https://docs.telematicssdk.com/platform-features/back-end-as-a-service
https://docs.telematicssdk.com/platform-features/fnol-inspections-and-damage-recognition/authorization
https://docs.telematicssdk.com/platform-features/car-service
Example of workflow
Example of workflow
Original photo and result of processing