Leapsome is an AI-powered people enablement platform unifying performance reviews, OKRs and goal tracking, engagement surveys, continuous feedback, competency frameworks, 1-on-1s, and learning. It aligns individual development with company objectives and runs structured review cycles and pulse surveys. Its Content API exposes goals, reviews, surveys, competencies, feedback, and meetings for people analytics.
Power end-to-end data operations for your Leapsome API with Nexla. Our bi-directional Leapsome connector is purpose-built for Leapsome, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Leapsome or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Leapsome workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
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.
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.
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.
Important
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.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter the Leapsome Content API secret token you generated in Prerequisites into the API Token field. Nexla will use this token to authenticate API requests as a Bearer token in the Authorization header 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.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Leapsome connector tile, then select the credential that will be used to connect to the Leapsome instance, and click Next; or, create a new Leapsome credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Leapsome endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
List Users
Retrieves all employees in your Leapsome organization, including profile details, employment status, manager relationships, team membership, and department. This endpoint is the foundation for all downstream joins across reviews, goals, and surveys, and is typically the starting point for any people analytics pipeline.
This endpoint uses automatic cursor-based pagination. Nexla manages page navigation automatically, so no manual pagination configuration is required.
Optionally, configure the following parameter to control the volume of records returned per API call:
Page Size: The number of user records to return per page. Accepts an integer up to a maximum of 100. Defaults to 100 if left blank.
The List Users endpoint returns all active and inactive employees accessible to the authenticated API token. Use this data to build org charts, join with review or goal data by user ID, or sync your Leapsome roster to external HR systems.
Get User
Retrieves full profile details for a single employee by their Leapsome user ID. Use this endpoint for targeted record refreshes, ID resolution workflows, or when you need the complete profile for a specific individual without fetching the entire roster.
Enter the Leapsome internal user ID in the User ID field. This field is required.
User IDs can be obtained by first running the List Users endpoint and extracting the id field from the response records.
This endpoint retrieves data for a single user in one API call. For bulk user data ingestion, use the List Users endpoint instead.
List Teams
Retrieves all teams and the department hierarchy defined in your Leapsome organization. Use this endpoint to build org chart analytics, segment review cycle data by team, or sync team structure to external BI tools.
This endpoint uses automatic cursor-based pagination managed by Nexla. No manual pagination configuration is required.
Optionally, configure the following parameter:
Page Size: The number of team records to return per page. Accepts an integer up to a maximum of 100. Defaults to 100 if left blank.
List Employee Attributes
Retrieves custom HR attribute definitions configured in Leapsome, such as salary band, tenure, location, or any other custom fields your organization has created. Use this endpoint to sync HR attribute metadata from Leapsome to external systems or to understand the schema of custom profile data before joining it with other employee records.
Page Size: The number of attribute records to return per page. Accepts an integer up to a maximum of 100. Defaults to 100 if left blank.
List Goals
Retrieves all goals in your Leapsome organization, including goal owner, associated team, current progress, status, linked competency, and due date. This is the primary OKR table and a key input for AI-powered goal generation and progress analytics.
This endpoint uses offset-based pagination. Nexla manages page advancement automatically.
Optionally, configure the following parameters:
Page Size: The number of goals to return per page. Accepts an integer up to a maximum of 100. Defaults to 100 if left blank.
Status Filter: Filters the returned goals by their current status. Leave blank to return goals at all statuses. Available status values are:
On Track — Goals currently progressing as planned.
At Risk — Goals that may not be completed on time without intervention.
Off Track — Goals that are behind schedule.
Completed — Goals that have been marked as complete.
Archived — Goals that have been archived.
To retrieve the full detail of a specific goal including its key results, sub-goals, and progress history, use the Get Goal endpoint with the goal ID obtained from this list.
Get Goal
Retrieves full detail for a single goal by its Leapsome goal ID, including key results, sub-goals, linked initiatives, progress history, and audit trail. Use this endpoint when you need the complete goal record for a specific objective.
Enter the Leapsome goal ID in the Goal ID field. This field is required.
Goal IDs can be obtained by first running the List Goals endpoint and extracting the id field from the returned records.
List Key Results
Retrieves all key results for a specific goal, including current and target values. Use this endpoint to enable automated OKR progress synchronization from CRM systems, Jira, or other external tools that track the underlying metrics.
Enter the parent goal's Leapsome ID in the Goal ID field. This field is required. Use the List Goals endpoint to obtain goal IDs.
This endpoint uses automatic cursor-based pagination. Nexla manages page navigation automatically. No additional pagination configuration is required.
Key result current and target values are returned as numeric fields. These values can be used as the input to the Update Key Result Progress destination endpoint to write progress back to Leapsome from an external system.
List Review Cycles
Retrieves all configured review cycles in Leapsome, including cycle type (such as 360-degree, annual, or project-based), current status, date range, and participant count. This endpoint is the entry point for any review data pipeline and is typically used to identify the cycle IDs needed for downstream review answer and assessment queries.
This endpoint uses automatic cursor-based pagination managed by Nexla.
Optionally, configure the following parameters:
Page Size: The number of review cycle records to return per page. Accepts an integer up to a maximum of 100. Defaults to 100 if left blank.
Status Filter: Filters the returned review cycles by status. Leave blank to return all cycles. Available status values are:
Active — Review cycles currently in progress.
Completed — Review cycles that have finished.
Draft — Review cycles that have been created but not yet launched.
Review cycle IDs returned by this endpoint are required parameters for the List Review Answers, List Review Assessments, and List Review Participants endpoints.
List Review Answers
Retrieves question scores and open-text responses for each reviewee/reviewer pair within a specific review cycle. This endpoint provides the raw answer corpus used for AI-powered review summaries, sentiment analysis, and people analytics dashboards.
Enter the Leapsome review cycle ID in the Review Cycle ID field. This field is required. Use the List Review Cycles endpoint to obtain cycle IDs.
This endpoint uses offset-based pagination. Nexla manages page advancement automatically.
Optionally, configure the following parameter:
Page Size: The number of answer records to return per page. Accepts an integer up to a maximum of 100. Defaults to 100 if left blank.
To interpret the meaning of individual questions and rating scales in the returned answers, pair this data with records from the List Review Templates endpoint.
List Review Assessments
Retrieves aggregated competency scores per employee for a specific review cycle. These assessment records are the primary input for AI-powered calibration tools, talent analytics, compensation decision support, and skill gap analysis.
Enter the Leapsome review cycle ID in the Review Cycle ID field. This field is required. Use the List Review Cycles endpoint to obtain cycle IDs.
This endpoint uses offset-based pagination. Nexla manages page advancement automatically.
Optionally, configure the following parameter:
Page Size: The number of assessment records to return per page. Accepts an integer up to a maximum of 100. Defaults to 100 if left blank.
List Review Templates
Retrieves review template structure, question bank, and rating scale definitions. This metadata is required for correctly interpreting raw review answer records — without knowing the question text and scale, numeric scores from List Review Answers cannot be properly analyzed.
Page Size: The number of review template records to return per page. Accepts an integer up to a maximum of 100. Defaults to 100 if left blank.
List Review Participants
Retrieves participant completion status for a specific review cycle. Use this endpoint to track review submission rates, monitor review cycle health metrics, and identify which reviewers have not yet completed their assigned reviews.
Enter the Leapsome review cycle ID in the Review Cycle ID field. This field is required. Use the List Review Cycles endpoint to obtain cycle IDs.
Page Size: The number of participant records to return per page. Accepts an integer up to a maximum of 100. Defaults to 100 if left blank.
List Surveys
Retrieves all survey instances in Leapsome, including survey type (engagement, pulse, onboarding, or exit), date range, and overall participation rate. This endpoint is the entry point for any survey data pipeline and provides the survey IDs needed for downstream result and comment queries.
Page Size: The number of survey records to return per page. Accepts an integer up to a maximum of 100. Defaults to 100 if left blank.
Survey Type Filter: Filters the returned surveys by type. Leave blank to return all surveys. Available type values are:
Engagement — Comprehensive engagement surveys.
Pulse — Short, frequent pulse check-ins.
Onboarding — Surveys sent to new hires during their onboarding period.
Exit — Surveys sent to departing employees.
Survey IDs returned by this endpoint are required parameters for the List Survey Results, List Survey Comments, and List Survey Questions endpoints.
List Survey Results
Retrieves aggregated score data broken down by question category and team segment for a specific survey. These results are the primary input for AI-powered sentiment analysis, engagement insight reports, and management dashboard metrics.
Enter the Leapsome survey ID in the Survey ID field. This field is required. Use the List Surveys endpoint to obtain survey IDs.
This endpoint uses offset-based pagination. Nexla manages page advancement automatically.
Optionally, configure the following parameter:
Page Size: The number of result records to return per page. Accepts an integer up to a maximum of 100. Defaults to 100 if left blank.
List Survey Comments
Retrieves anonymized open-text responses submitted in a specific survey. These comments are the primary corpus for AI-powered theme extraction, natural language processing (NLP) analysis, and sentiment pipelines. Leapsome returns these responses anonymized to protect respondent identity.
Enter the Leapsome survey ID in the Survey ID field. This field is required. Use the List Surveys endpoint to obtain survey IDs.
This endpoint uses offset-based pagination. Nexla manages page advancement automatically.
Optionally, configure the following parameter:
Page Size: The number of comment records to return per page. Accepts an integer up to a maximum of 100. Defaults to 100 if left blank.
Survey comments are anonymized by Leapsome and do not contain individual respondent identifiers. Use this data for aggregate text analysis rather than per-respondent tracking.
List Survey Questions
Retrieves the question text, question type, and category for all questions in a specific survey. This metadata is required to decode survey score and comment records returned by List Survey Results and List Survey Comments for downstream analytics.
Enter the Leapsome survey ID in the Survey ID field. This field is required. Use the List Surveys endpoint to obtain survey IDs.
This endpoint returns all questions in a single call without pagination.
List Competencies
Retrieves all competencies defined in Leapsome, along with their seniority levels, behavioral descriptions, and linked roles. This data is the source for AI-powered competency framework generation, skill recommenders, and career path analysis tools.
Page Size: The number of competency records to return per page. Accepts an integer up to a maximum of 100. Defaults to 100 if left blank.
Competency IDs returned by this endpoint are required parameters for the List Competency Scores and List Competency Levels endpoints.
List Competency Scores
Retrieves per-user scores for a specific competency over time. Use this data to power skill gap analysis, learning and development (L&D) recommendations, and compensation calibration workflows.
Enter the Leapsome competency ID in the Competency ID field. This field is required. Use the List Competencies endpoint to obtain competency IDs.
This endpoint uses offset-based pagination. Nexla manages page advancement automatically.
Optionally, configure the following parameter:
Page Size: The number of score records to return per page. Accepts an integer up to a maximum of 100. Defaults to 100 if left blank.
List Competency Levels
Retrieves the level definitions for each seniority band associated with a specific competency. This metadata provides the context needed for calibration discussions, career framework design, and compensation decisions.
Enter the Leapsome competency ID in the Competency ID field. This field is required. Use the List Competencies endpoint to obtain competency IDs.
This endpoint returns all level definitions for the specified competency in a single call without pagination.
List Instant Feedback
Retrieves real-time feedback events from the Leapsome continuous feedback stream, including the giver, receiver, associated competency tag, and feedback text. This endpoint is the primary data source for people analytics involving continuous feedback, coaching pattern analysis, and culture metrics.
This endpoint uses offset-based pagination. Nexla manages page advancement automatically.
Optionally, configure the following parameters to filter feedback by date range:
From Date: The start of the date range for feedback events to include. Accepts ISO 8601 format (for example, 2024-01-01T00:00:00Z). Defaults to 90 days before the current date ({now-90}) if left blank.
To Date: The end of the date range for feedback events to include. Accepts ISO 8601 format (for example, 2024-12-31T23:59:59Z). Defaults to the current datetime ({now}) if left blank.
Page Size: The number of feedback records to return per page. Accepts an integer up to a maximum of 100. Defaults to 100 if left blank.
The default date range of 90 days is suitable for incremental loads. For an initial historical backfill, set the From Date to the earliest date for which your organization has feedback data in Leapsome.
List Meetings
Retrieves 1-on-1 meeting records from Leapsome, including agenda completion status, outstanding action items, attendees, and meeting date. Use this endpoint to analyze manager-employee meeting cadence, track action item follow-through, and integrate meeting outcomes with project management tools.
This endpoint uses offset-based pagination. Nexla manages page advancement automatically.
Optionally, configure the following parameters to filter meetings by date range:
From Date: The start of the date range for meeting records to include. Accepts ISO 8601 format (for example, 2024-01-01T00:00:00Z). Defaults to 90 days before the current date ({now-90}) if left blank.
To Date: The end of the date range for meeting records to include. Accepts ISO 8601 format (for example, 2024-12-31T23:59:59Z). Defaults to the current datetime ({now}) if left blank.
Page Size: The number of meeting records to return per page. Accepts an integer up to a maximum of 100. Defaults to 100 if left blank.
Meeting IDs returned by this endpoint are required when using the Create Meeting Action Item destination endpoint to write action items back to Leapsome from external meeting tools.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Leapsome data sources can also be manually configured to ingest data from any valid Leapsome API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
All Leapsome Content API endpoints begin with https://api.leapsome.com/v1/ — for example, https://api.leapsome.com/v1/users. Leapsome list endpoints wrap records in a top-level data array alongside pagination metadata (for example, {"data": [...], "nextPageToken": "..."}), so set the path to data to $.data[*]. For single-record endpoints such as Get User or Get Goal, use $ to return the entire response object as one record. Date-filtered endpoints such as List Instant Feedback and List Meetings accept from/to macros in the API URL.
You do not need to include the Authorization header — Nexla automatically adds the Bearer token from your Leapsome credential to every request.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Leapsome data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Leapsome destination, and select the Send to Destination option from the menu. Select the Leapsome connector from the list of available destination connectors, then select the credential that will be used to connect to the Leapsome organization, and click Next; or, create a new Leapsome credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Leapsome write endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Update Goal Progress
Writes the current progress value to a Leapsome goal from an external system. This is the primary automation use case for Leapsome's API — it allows CRM metrics, project tracking tools, or any external data source to automatically push progress updates to Leapsome goals without manual entry.
Enter the Leapsome goal ID in the Goal ID field. This field is required. The goal ID identifies which goal in Leapsome will receive the progress update.
Goal IDs can be obtained by first reading data from Leapsome using the List Goals source endpoint and extracting the id field from the returned records.
The request body sent to Leapsome must include a currentValue field containing the numeric progress value. Ensure that the Nexset field carrying the progress value is mapped to currentValue in the data transformation step before this destination.
This endpoint sends a POST request to https://api.leapsome.com/v1/goals/{goalId}/progress. The Leapsome API will update the goal's current progress value and recalculate its status (On Track, At Risk, or Off Track) based on the new value relative to the target.
Update Key Result Progress
Writes the current progress value to a specific key result within a Leapsome goal. This enables CRM-to-OKR pipeline automation at the key result (KR) level, allowing individual key results to be automatically updated from external metric sources such as Salesforce, Jira, or a data warehouse.
Enter the parent goal's Leapsome ID in the Goal ID field. This field is required and identifies the goal that contains the key result to be updated.
Goal IDs can be obtained from the List Goals source endpoint.
Enter the Leapsome key result ID in the Key Result ID field. This field is required and identifies the specific key result to update within the parent goal.
Key result IDs can be obtained from the List Key Results source endpoint by specifying the parent goal ID.
The request body sent to Leapsome must include a currentValue field containing the numeric progress value. Ensure that the Nexset field carrying the updated metric is mapped to currentValue in the data transformation step before this destination.
This endpoint sends a POST request to https://api.leapsome.com/v1/goals/{goalId}/key-results/{krId}/progress. Updating a key result's progress also affects the parent goal's overall progress, as Leapsome recalculates goal progress based on the weighted contribution of its key results.
Create Instant Feedback
Pushes feedback events from external tools — such as Slack, Microsoft Teams, Jira, or a custom recognition tool — directly into the Leapsome continuous feedback stream. This allows organizations to centralize all employee feedback in Leapsome regardless of where it originates.
This endpoint does not require any URL path parameters. Nexla sends the entire Nexset record as a JSON body to the Leapsome instant feedback endpoint.
Ensure that the Nexset fields are mapped to the appropriate Leapsome feedback payload fields before this destination. Consult the Leapsome API documentation for the full list of required and optional body fields for the instant feedback creation endpoint.
Feedback submitted via the API appears in the Leapsome platform in the same way as feedback submitted manually through the UI. Recipients receive notifications through their configured Leapsome notification settings.
Create Meeting Action Item
Writes action items from external meeting tools — such as Zoom, Google Meet, or Notion — back into a Leapsome 1-on-1 meeting record. This keeps meeting follow-up actions synchronized between Leapsome and the tools your teams use to run meetings.
Enter the Leapsome meeting ID in the Meeting ID field. This field is required and identifies which 1-on-1 meeting record will receive the new action item.
Meeting IDs can be obtained from the List Meetings source endpoint.
Nexla sends the Nexset record as a JSON body to the Leapsome meeting action items endpoint. Ensure that Nexset fields are mapped to the appropriate Leapsome action item payload fields. Consult the Leapsome API documentation for required body fields.
Action items created via the API appear in the Leapsome meeting record and are visible to all meeting participants. They can be tracked and marked as complete within Leapsome.
Leapsome destinations can also be manually configured to send data to any valid Leapsome API endpoint. Using manual configuration, you can also configure Nexla to automatically send the response received from the Leapsome API after each call to a new Nexla webhook data source. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
All Leapsome Content API endpoints begin with https://api.leapsome.com/v1/, and the API accepts JSON request bodies for all write operations — select JSON as the content format. Common write operations use POST to create resources or write progress updates (for example, https://api.leapsome.com/v1/goals/{'{goalId}'}/progress), PUT to fully replace a resource, and PATCH for partial updates. For endpoints that write to a specific resource, include the resource ID at the appropriate position in the URL path.
You do not need to include the Authorization header — Nexla automatically adds the Bearer token from your Leapsome credential to every request. Most Leapsome write endpoints (such as Update Goal Progress and Update Key Result Progress) are designed to receive one record per API call, so leave record batching disabled unless the target endpoint accepts bulk payloads.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To begin sending data to the configured Leapsome endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to Leapsome until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
