Skip to main content

Authorization

Follow this guide to create a new Skedulo credential that will allow Nexla to authenticate to and exchange data with your Skedulo account.
skedulo_api_auth.png

Skedulo

Prerequisites​

To connect Nexla to Skedulo, you need a Skedulo API token and the correct regional base URL for your tenant. Skedulo API tokens are created through the Skedulo web application by users with administrator permissions.

Obtain a Skedulo API Token​

Skedulo supports both long-lived (non-expiring) and time-limited API tokens. For integration use cases such as connecting to Nexla, a long-lived token is recommended so that your data flows continue to operate without requiring periodic credential updates.

  1. Log in to the Skedulo web application as an administrator.

  2. Click your user profile icon in the upper-right corner of the screen, then navigate to Settings > Developer Tools > API Tokens.

  3. Click the Create button to open the token creation dialog.

  4. In the token creation dialog, set the Expires field to Never to generate a long-lived token (recommended for integrations), or select a specific expiry duration if your organization requires time-limited tokens.

  5. Enter a descriptive name for the token (for example, Nexla Integration) to help identify it later.

  6. Click Create to generate the token.

Important

Copy the API token immediately after it is generated and store it in a secure location. The full token value is only displayed once — it cannot be retrieved again after you navigate away from this screen.

  1. Save the copied token value to use when creating your Nexla credential.

Additional information about Skedulo API tokens, including how to create tokens programmatically via the REST API, is available in the Skedulo authentication documentation.

Identify Your Regional Base URL​

Skedulo tenant instances are deployed in one of four geographic regions. You must use the base URL that corresponds to the region where your tenant is hosted.

RegionBase URL
United Stateshttps://api.skedulo.com
United Kingdomhttps://api.uk.skedulo.com
Canadahttps://api.ca.skedulo.com
Australiahttps://api.au.skedulo.com

Contact your Skedulo administrator if you are not certain which region your tenant is deployed in. You can also determine your region by checking the URL you use to log in to the Skedulo web application — the subdomain typically reflects the region.

Create a Skedulo Credential​

  • To create a new Skedulo credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

Credential Name & Description​

  1. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

    Resource descriptions are recommended but are not required. They should be used to provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.

API Token Authentication​

Skedulo uses API token authentication. The token is transmitted as a Bearer token in the Authorization HTTP request header for all API calls.

  1. Enter your Skedulo API token in the API Token field. This is the long-lived or time-limited token you generated in the Skedulo web application under Settings > Developer Tools > API Tokens. The token value is treated as a password and will be masked after it is saved.

  2. Select or enter the Regional Base URL that corresponds to your Skedulo tenant's deployment region:

    • US (api.skedulo.com) — https://api.skedulo.com
    • UK (api.uk.skedulo.com) — https://api.uk.skedulo.com
    • CA (api.ca.skedulo.com) — https://api.ca.skedulo.com
    • AU (api.au.skedulo.com) — https://api.au.skedulo.com

    Selecting the incorrect regional base URL will result in authentication failures, even if the API token itself is valid. Ensure you select the region that matches your Skedulo tenant's deployment location.

Save the Credential​

  1. Once all of the relevant steps in the above sections have been completed, click the Save button at the bottom of the overlay to save the configured credential.

  2. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.