Classes

Zendrive Object.

ZendriveAccidentInfo

Wrapper for meta-information related to an accident detected by the SDK.

Information about the active drive if any.

This contains the fully analyzed results for a drive, this is returned from -[ZendriveDelegateProtocol processAnalysisOfDrive:] callback for all the trips with the value of ZendriveDriveInfo.driveType not set to ZendriveDriveType.ZendriveDriveTypeInvalid.

The data of this type will always be of equal or better quality than ZendriveEstimatedDriveInfo returned from -[ZendriveDelegateProtocol processEndOfDrive:]

Typically -[ZendriveDelegateProtocol processAnalysisOfDrive:] will be fired within a few seconds after -[ZendriveDelegateProtocol processEndOfDrive:] callback but in some rare cases this delay can be really large depending on phone network conditions.

The callback for this -[ZendriveDelegateProtocol processAnalysisOfDrive:] will be fired in trip occurrence sequence, i.e. from oldest trip to the latest trip.

This class contains parameters required by Zendrive during setup.

Utility class which helps in uploading data required for debugging Zendrive SDK related issues.

ZendriveDriveInfo

Wrapper for meta-information related to a drive.

Information about a drive that was resumed in the Zendrive SDK.

This is called after the drive recording resumes after a gap. The gap may occur due to an application restart by the OS, application kill and restart by a user, an application crash etc.

Driving Behaviour scores for a drive.

The scores are expressed as a number between 0 to 100 and will be -1 if not available.

High scores indicate safe driving and low scores reflect hazardous or risky driving patterns. Preventive or corrective actions should be prescribed in extreme cases.

More information is available here

Information about start of a drive.

Additional attributes of a Zendrive driver.

The application can specify both predefined and custom attributes for a driver. These attributes are associated with a SDK driverId at SDK initialization time. In addition to predefined special attributes, up to 4 custom key value attributes can be associated with a driver using the Zendrive SDK.

This contains the best estimated results for a drive, this is returned from -[ZendriveDelegateProtocol processEndOfDrive:] callback.

The data of this type will always be of same or little bad quality than ZendriveAnalyzedDriveInfo returned from -[ZendriveDelegateProtocol processAnalysisOfDrive:]

All drives with driveType not set to ZendriveDriveTypeInvalid will get a corresponding -[ZendriveDelegateProtocol processAnalysisOfDrive:] callback.

Typically -[ZendriveDelegateProtocol processAnalysisOfDrive:] will be fired within a few seconds after -[ZendriveDelegateProtocol processEndOfDrive:] callback but in some rare cases this delay can be really large depending on phone network conditions.

A valid object of this class is returned in ZendriveEvent.speedingData whenever ZendriveEvent.eventType is equal to ZendriveEventOverSpeeding.

Represents a driving behavior event like phone use, aggressive acceleration etc. It is part of ZendriveDriveInfo object of -[ZendriveDelegateProtocol processEndOfDrive:] callback.

Represents ratings associated with the various event types for a trip. Higher rating for an event represents safe driving behaviour with respect to that event. For cases where rating is absent, ZendriveStarRatingNA is reported.

Class for providing feedback back to Zendrive

Applications which want to record Fairmatic insurance periods for a driver may use these APIs.

All drives (automatically detected or manually started) when a period is in progress will be tagged with the period id. This period id will be made available in the reports and API that Fairmatic provides via Zendrive.

Only one period can be active at a time. Switching periods or calling +stopPeriod: stops any active drives (automatic or manual). A drive with multiple insurance periods will be split into multiple trips for different insurance periods.

Represents a geographical coordinate.

Represents the current state of the Zendrive SDK.

This class contains methods that mock Zendrive’s functionality for testing purposes.

Represents a single warning that might have occurred during your trip. A collection of these warnings are provided using the -[ZendriveDelegateProtocol processAnalysisOfDrive:] callback.