Authorization
Leapsome
Prerequisites
Leapsome uses a dedicated Content API for programmatic access to goals, reviews, surveys, competencies, feedback, and meeting data. You must generate a Content API secret token from within Leapsome before creating a credential in Nexla.
Generate a Leapsome Content API Token
The Content API token is generated inside the Leapsome admin settings. Only Leapsome administrators with access to the Integrations and imports settings can create API tokens.
-
Sign in to your Leapsome account at leapsome.com.
-
Click your profile or company name in the upper area of the page to access the main navigation, then navigate to Settings > Integrations and imports > API access.
-
On the API access page, click the Create API Secret button. Leapsome will generate a new API token and display it at the top of the page.
Copy the API token immediately after it is generated. Leapsome displays the token only once — if you navigate away without saving it, you will need to regenerate a new token. Store the token securely, such as in a password manager, as it grants access to your organization's Leapsome data.
- The generated token serves as a Bearer token for all API requests. Nexla will use this token to authenticate calls to the Leapsome Content API at the base URL
https://api.leapsome.com/v1.
The Leapsome Content API provides access to Reviews and Goals data as well as the broader set of people data endpoints — including users, teams, surveys, competencies, instant feedback, and meetings. For full API reference documentation, see the Leapsome API documentation.
Create a Leapsome Credential
- To create a new Leapsome credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Credential Name & Description
-
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
-
Enter the Leapsome Content API secret token you generated in the Prerequisites section into the API Token field. Nexla will use this token to authenticate API requests as a Bearer token in the
Authorizationheader of every call to the Leapsome API.The API Token field is treated as a secure (password-type) field. Once saved, the token value will not be displayed again in the Nexla interface. If the token needs to be rotated, generate a new token in Leapsome and update the credential in Nexla.
Save the Credential
-
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.
-
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.