The developer tools section of admin settings allows admins to create long-lived API tokens for use with the Skedulo APIs.
Access to the admin settings is provided via the user profile button (at the top-right of the console).
In the developer tools section the following settings can be configured:
The logged-in user can view their details which contain the following:
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).
API Tokens can be used to access the Skedulo API as a particular user without requiring them 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:
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.
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).
When the Skedulo web app loads (at log in or when the browser is reloaded), users will see an alert (via warning toast notification) if they have exceeded one or more of their Salesforce event API limits.
Exceeding these limits may prevent the following functionality:
Web app real-time updates for changes to jobs and allocations.
Mobile notifications for:
Shifts that are created, moved or modified.
Webhooks, triggered actions, and GraphQL subscriptions (may include per job chat functionality).
If users see this warning they should contact their Skedulo Customer Success Manager.