Using in .NET
The .NET SDK tools provide an easy way to integrate MyGeotab into .NET software. All of the communication to Geotab’s services is accomplished over HTTPS with data serialized in JSON format. The .NET library provided will automatically handle the JSON serialization and deserialization into MyGeotab objects.
Including this assembly in the project allows for the interaction with the Geotab API. It is a convenient “wrapper” around Geotab’s HTTP/JSON API to allow developers focus on writing code instead of moving data over the wire. It includes tools to assist authenticating against Geotab’s servers, automatically serializing/deserializing JSON, and providing definitions for Checkmate object classes.
Download the Geotab.Checkmate.ObjectModel.dll and .NET examples from the .NET example ZIP file and add a reference to it from the .NET project.
In order to have access to the API class, add the following to the file’s includes section:
An instance of API can now be constructed to be used in the code. For the most basic use case, all the data that is needed is user credentials and a database name:
At this point there has not been any communication with Geotab’s servers. In order to make calls to Geotab’s API, an authentication call must be made:
When the call is made to Geotab’s servers to authenticate, a token is returned for security. For more information regarding how Geotab handles authentication, please review the “Authentication” section in the Concepts documentation.
Behind the scenes, the Authenticate call makes a JSON-RPC request to Geotab’s “Authenticate” method. The resulting security token and server information are stored in order to make further calls to the API.
When authenticated, calls are made to the API by invoking the “Call” method of the API class.
The example below illustrates how to make a generic call to get all devices in the system.
In the example below it is shown how to delete a device using the generic “Remove” method. Notice that it is not required to send all of the device’s information to remove it, the device’s id is sufficient:
The last parameter to this Call method is an anonymous object which contains the parameters for the method (please review the API reference to see which parameters the method expects, and whether the parameters are required or optional). The parameter order is not significant, and it is acceptable to omit optional parameters. Optional parameters will revert to their default values, typically “null” or “false” values.
The API class automatically handles databases that are moved to different servers in the federation and expired tokens (token are typically valid for 2 weeks) by automatically re-authenticating and continuing.
The following is a simple console app that will output the latitude and longitude of each device in a list of devices:
After entering your credentials into the API constructor, this example will produce results similar to this in your command prompt window.
Once you have a basic understanding of how the .NET SDK works, we recommend reviewing the examples that we have created here.