How to make an API Token step by step
Carriers must share the following elements in order to perform automated tracking with this GPS:
- API Token
API Token
Previous considerations
ATTENTION: Only the following user roles have permissions to create API TOKENS:
- Full Admin
- Standard Admin
- A custom role created by your organization, containing the following permissions:
1) edit permissions to view and edit API TOKENS and
2) edit permissions to create, edit, and delete users, roles, and tags.
In either case, users must have access to the ENTIRE ORGANIZATION.
If you don't see the API TOKENS options below, please check and make sure you have a user with sufficient permissions.
How to make an API Token step by step
Click the SETTINGS gear at the bottom of your Samsara dashboard to access the configuration options.
Once in the settings list, click DEVELOPER - API TOKENS.
Click on ADD API TOKEN in the top right corner.
Next, define the token properties:
- NAME. We recommend that it be descriptive and easy to identify. For example, FR8APP.
- TAG ACCESS. Select the tag access level.
- PERMISSION SCOPE. Select the token scope and permissions. Simply grant READ-ONLY permissions in the Global drop-down.
The API TOKEN consists of two elements: name and token, which will appear at the top of the screen.
It's very important that you copy and save these two elements immediately, as once you copy it and/or refresh the page, the token's text will no longer be visible.
Please share the access token with our integrations team.
If you don't write it down and need to see it in the future, you'll need to REGENERATE the token.
Example of a valid API Token
This is what a Samsara API Token looks like:
It has 2 elements
- Name
- Access token