Start with Server APIs

Zendrive Server APIs provide driver transactional information and analytics metrics at various aggregation levels via URI paths. To use these APIs, your application should make a HTTPS request and parse the response. Use standard HTTP GET methods to retrieve driver data.

We support cross-origin resource sharing to allow you to interact securely with our API from a client-side web application. The response format is JSON for all responses from the API, including errors.

Since the API is based on open standards, you can use any web development language to access the API.

Before You Begin

Get acquainted with the following concept:

API Host and Versioning: All API requests must be sent to https://api.zendrive.com and must contain the appropriate version in the path. The current API version is v4, for all APIs in SDK 8.3, except the newly introduced Beacon APIs, which bear the version v1.

Scale

Our current APIs are scalable for fleets up to 100,000 drivers.

API Query Limits

Zendrive Server APIs currently support up to 5 queries per second. If you need to temporarily increase the API query limits, contact [email protected].

Authentication

Authenticate to the server API by providing your application key in the API header. The application key must be specified as the APIKEY parameter. It is a required parameter in every API request.

-H 'Authorization: APIKEY sample_api_key'

All API requests must be made over HTTPS. Calls made over HTTP will fail.

Sign Up to get your API key.

Your API key carries many privileges, so keep it secret and secure. Never expose your secret API key in any public website’s client-side code, and never make server API calls from mobile apps.

Errors

The server APIs use conventional HTTP response codes to indicate success or failure of an API request.

• Response codes in the 2xx range indicate success

• Response codes in the 4xx range indicate an error that resulted from the provided information (e.g. a required parameter was missing)

• Response codes in the 5xx range indicate an error with Zendrive’s servers.

The error response JSON may have the following attributes.

Attribute	Description
error	A human readable message giving more details about the error.

About Zendrive Scores

The safety and efficiency of your fleet drivers can make or break your bottom line. The Zendrive SDK was built to give fleet managers insight into the quality and safety of their drivers based on detailed driving behavior.

By accessing phone sensors and combining that data with context about the drive time and place, Zendrive can identify both safe and risky driving, allowing fleet managers to take action before poor driving becomes a liability.

Zendrive mobile SDK automatically trips and collects sensor data (GPS / accelerometer / gyroscope and so on) throughout the trip. Zendrive employs state of the art data analysis and machine learning algorithms to compute various driver behavior scores. The overall Zendrive Score is expressed as a number between 0 to 100, with a higher value corresponding to better driving practices.

Drivers are also rated on individual driving events such as harsh braking, aggressive acceleration, speeding, hard turns and phone use. Individual event ratings are on a scale from 1-5, with 5 being the highest. In a customer-facing application, this can be expressed as a simple number.