The developer tools section of admin settings allows admins to create long-lived API tokens for use with the Skedulo APIs.
In the developer tools section the following settings can be configured:
The logged in user can view their details which contain the following:
- Full Name.
- Tenant ID (a handy "copy to clipboard" button is provided).
- Session Token (a handy "copy to clipboard" button is provided).
- Session Token Expiry.
- Salesforce Access Token (a handy "copy to clipboard" button is provided).
Figure 1. The admin settings for developer tools.
API Tokens can be used to access the Skedulo API as a particular user without requiring that user to log in. The user must be a Skedulo admin.
To use the API token, include it in the Authorization header of the HTTP request as follows:
Important! The generated API token may be used to access any Skedulo API services as the currently logged in user.
The generated token is secret to you and is not saved by Skedulo—once the "Create an API" modal is closed it is gone (it is not recoverable). We recommend that you copy the token to a secure location immediately, such as a password vault. Also, make a note of the "Token Id" and the service it provides as this can be used to revoke access to the token at a later date.
Tokens can be revoked via the same "API Tokens" settings panel.
Figure 2. The API token section of developer tools.
Figure 3. Creating an API token with expiry options.
Figure 4. An example of a generated token with its token id ready to be copied.
Also, see Admin Settings: Connected Pages.
Using the information on this tabbed view, organizations can determine exactly how many API calls are being made by Skedulo (includes all calls to the Salesforce API—web, mobile, custom forms, 3rd party integrations that may not be Skedulo related).
The logged in user can view the following details:
- Salesforce Access Token.
- Daily API Usage (the current daily Salesforce API usage).
Figure 5. The Salesforce section of developer tools.