Authentication Workflow

The v3 endpoints support authentication using JWT tokens that are generated by making a request to our authentication API using the user's credentials. Once the token is obtained, it needs to be added to the header of every request by prefixing the word "Bearer" before the token.

Here's a simple request to get all vehicles in the account. Notice the use of the bearer token in the request header.

curl -L -X POST '' \
-H 'Authorization: Bearer w2jSAxPG8IeaKJMcFaEGxTB1tj5XS9Q2y' \
-H 'Content-Type: application/json' \
--data-raw '{}'

Since the token is generated for a user account, the user's permissions/roles will apply to API operations as well. For example, a user that does not have access to create geofences will not be able to create geofences using the APIs as well.


Token Expiration & Refresh

It is recommended to refresh the token as often as possible. Since our v3 APIs are in limited beta as of today, the token expires every 180 days. This may change once we have a production release.