This guide describes the general flow for ETL users to consume Geotab Data Connector. OData Connector implemented OData protocol V4, or you may consider it just as a RESTful service.
Before making your first call, it is strongly recommended to skip the general entry and make the call directly to OData Connector. If you are not sure what the URL to call is, please contact the support team.
Feel free to skip this section if you plan to make calls directly to OData Connector. If you have to make a call to the general entry (https://data-connector.geotab.com), make sure you are ready to handle the 302 response and make another call to the returned URL.
Sample general entry response:
If you are making calls to the general entry with postman or insomnia, the 400 error code is expected since postman or insomnia redirect requests WITHOUT the auth header.
Given the right url, you may test the service connection by making calls to the service root: https://odata-connector-1.geotab.com/odata/v4/svc/
No credential is required for this service root.
Sample request:
Sample response:
Make sure to attach one of the above table names after the service root and attach your base64 encoded credentials in the following format: <database>/<username>:<password></password>
e.g. abccompany/geotab-data-connector@geotab.com:password Sample request:
Sample response:
You can also specify a date range as the query option, for more information about the query option, see here.
The following example shows how to consume OData Connector with Python, feel free to use any programming language, library or framework. Dependencies:
Setup credential and query options:
Get data from latest vehicle metadata and visualization:
Get data from vehicle KPI table with date range:
Please refer to Geotab Data Connector - Data Schema and Dictionary for current available data and details about table schema.