-
Notifications
You must be signed in to change notification settings - Fork 0
User Guide
Before we move on to APIs, we need to know the concept behind the working of digiTreck.
###Project
In the digiTreck, a project is a collection of access keys, credentials, and rules about the application or applications you're working on that make use of digiTreck Platform. The dashboard is where you manage certain project tasks, such as generating creating Access Keys, enabling APIs, and managing team and billing information associated with your project.
###Access Keys
An Access key is a unique identifier that you generate using the dashboard. An Access Key can be used to identify a server or a group of devices. Using an Access key does not require user action or consent. Access keys do not grant access to any account information, and are not used for authorization.
In digiTreck, we have 2 type of Access keys :
-
Server Key : Enables servers to connect to digiTreck APIs. Using the Private Key to genarate HASH to authorise the API calls.
-
Device Key : Enables devices to connect to digiTreck APIs. Used as group identifier for devices.
Example
If your application has Consumer and Driver type devices, then you need to create 2 Device keys for both.
Respective device keys will help you identify the type of devices.
Use an Access key when your application is running on a server and accessing one of the following kinds of data:
###Device
Device signifies any mobile entity, whose location needs to be tracked. Devices upload their location and track other devices, using the digiTreck SDK.
Currently, only Android SDK is available.
But we are working hard to bring you iOS and Windows SDK as soon as possbile.