ChartHop is an org chart and people-analytics platform for HR, compensation planning, and workforce management. It centralizes people data such as employees, jobs, org structure, compensation bands, budgets, goals, and time off, and exposes this data through a REST API. Nexla connects to the ChartHop API to ingest this workforce data and to write updates back to your organization.
Power end-to-end data operations for your ChartHop API with Nexla. Our bi-directional ChartHop connector is purpose-built for ChartHop, 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 ChartHop or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your ChartHop 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
Before creating a ChartHop credential, you need a ChartHop API authorization token and your organization's ID (or slug). ChartHop authenticates API requests with a token sent as a Bearer token in the Authorization header.
To obtain your ChartHop credentials, follow these steps:
Email support@charthop.com with the subject line "new app request" to request an app install for your organization. In your request, include your app name, organization name, a short app description, the permission levels your integration needs, whether the app is for your org only or for distribution, and whether you will use the REST API, webhooks, or both.
Once your request is approved, ChartHop creates and installs an app in your organization's account and issues an API authorization token that can be used to access the REST API on behalf of the app. Store this token securely, as it grants access to your organization's people data.
Identify your Org ID (or slug), the ChartHop organization identifier that this connection accesses. You can find it in ChartHop under your org settings, or by calling GET /v1/org with your token.
ChartHop API authorization token. Obtained by requesting an app install from ChartHop (email support@charthop.com); ChartHop then issues an API authorization token for your org.
Org ID
Yes
No
ChartHop organization identifier (or slug) that this connection accesses. Found in ChartHop under org settings, or via GET /v1/org.
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 your ChartHop API authorization token in the API Token field. This token is sent as a Bearer token in the Authorization header for all API requests and must be kept confidential.
Enter your ChartHop organization identifier in the Org ID field. This is the org ID or slug that this connection will access, obtained in Prerequisites.
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 ChartHop connector tile, then select the credential that will be used to connect to the ChartHop organization, and click Next; or, create a new ChartHop 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 ChartHop 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.
Find Persons
Find persons (employees) in the organization.
This endpoint returns a paginated list of persons in your organization. Use the Page Size parameter to control the number of results returned per page (default 100). Nexla automatically follows the next-token pagination to fetch subsequent pages of data.
Find Orgs
Return all visible orgs, paginated by name.
This endpoint returns a paginated list of all orgs visible to your token. Use the Page Size parameter to control the number of results returned per page (default 100). Nexla automatically follows the next-token pagination to fetch subsequent pages of data.
Find Jobs
Find jobs in the organization.
This endpoint returns a paginated list of jobs in your organization. Use the Page Size parameter to control the number of results returned per page (default 100). Nexla automatically follows the next-token pagination to fetch subsequent pages of data.
Find Job Codes
Return all job codes in the organization, paginated.
This endpoint returns a paginated list of job codes in your organization. Use the Page Size parameter to control the number of results returned per page (default 100). Nexla automatically follows the next-token pagination to fetch subsequent pages of data.
Find Groups
Find groups (e.g. departments, teams) in the organization of a certain type.
This endpoint returns a paginated list of groups, such as departments or teams, in your organization. Use the Page Size parameter to control the number of results returned per page (default 100). Nexla automatically follows the next-token pagination to fetch subsequent pages of data.
Find Comp Bands
Find compensation bands in the organization.
This endpoint returns a paginated list of compensation bands in your organization. Use the Page Size parameter to control the number of results returned per page (default 100). Nexla automatically follows the next-token pagination to fetch subsequent pages of data.
Find Budgets
Find budgets in the organization.
This endpoint returns a paginated list of budgets in your organization. Use the Page Size parameter to control the number of results returned per page (default 100). Nexla automatically follows the next-token pagination to fetch subsequent pages of data.
Find Comp Reviews
Find compensation reviews in the organization.
This endpoint returns a paginated list of compensation reviews in your organization. Use the Page Size parameter to control the number of results returned per page (default 100). Nexla automatically follows the next-token pagination to fetch subsequent pages of data.
Find Goals
Find goals in the organization.
This endpoint returns a paginated list of goals in your organization. Use the Page Size parameter to control the number of results returned per page (default 100). Nexla automatically follows the next-token pagination to fetch subsequent pages of data.
Find Roles
Return all or a set of roles in the organization.
This endpoint returns a paginated list of roles in your organization. Use the Page Size parameter to control the number of results returned per page (default 100). Nexla automatically follows the next-token pagination to fetch subsequent pages of data.
Find Time Off Requests
Retrieve time off requests.
This endpoint returns a paginated list of time off requests in your organization. Use the Page Size parameter to control the number of results returned per page (default 100). Nexla automatically follows the next-token pagination to fetch subsequent pages of data.
Find Time Off Policies
Return all time off policies in the organization.
This endpoint returns a paginated list of time off policies in your organization. Use the Page Size parameter to control the number of results returned per page (default 100). Nexla automatically follows the next-token pagination to fetch subsequent pages of data.
Find Events
Return past events, paginated, without payloads present.
This endpoint returns a paginated list of past events in your organization, without event payloads present. Use the Page Size parameter to control the number of results returned per page (default 100). Nexla automatically follows the next-token pagination to fetch subsequent pages of data.
Find Files
Return a list of files.
This endpoint returns a paginated list of files in your organization. Use the Page Size parameter to control the number of results returned per page (default 100). Nexla automatically follows the next-token pagination to fetch subsequent pages of data.
Find Customers
Return all visible customers, paginated by name.
This endpoint returns a paginated list of all customers visible to your token. Use the Page Size parameter to control the number of results returned per page (default 100). Nexla automatically follows the next-token pagination to fetch subsequent pages of data.
Get Person
Return a particular person by id.
This endpoint returns a single person record. Provide the Person ID of the person to fetch.
Get Job
Return a particular job by id.
This endpoint returns a single job record. Provide the Job ID of the job to fetch.
Get Org
Return a particular org by id.
This endpoint returns a single org record for the organization associated with your credential.
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.
ChartHop data sources can also be manually configured to ingest data from any valid ChartHop 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.
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 ChartHop 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 ChartHop destination, and select the Send to Destination option from the menu. Select the ChartHop connector from the list of available destination connectors, then select the credential that will be used to connect to the ChartHop organization, and click Next; or, create a new ChartHop credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common ChartHop 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.
Create Person
Create a person.
This endpoint sends each record from your Nexset as a JSON request body to create a new person in your organization. The request body should contain the person data in the format required by the ChartHop API.
Update Person
Update an existing person.
This endpoint updates an existing person. Provide the Person ID of the person to update; each record from your Nexset is sent as a JSON request body containing the fields to update.
Delete Person
Delete a person.
This endpoint deletes an existing person. Provide the Person ID of the person to delete.
Create Job
Create a job.
This endpoint sends each record from your Nexset as a JSON request body to create a new job in your organization. The request body should contain the job data in the format required by the ChartHop API.
Update Job
Update an existing job.
This endpoint updates an existing job. Provide the Job ID of the job to update; each record from your Nexset is sent as a JSON request body containing the fields to update.
Delete Job
Delete a job.
This endpoint deletes an existing job. Provide the Job ID of the job to delete.
Create Goal
Create a goal.
This endpoint sends each record from your Nexset as a JSON request body to create a new goal in your organization. The request body should contain the goal data in the format required by the ChartHop API.
Update Goal
Update an existing goal.
This endpoint updates an existing goal. Provide the Goal ID of the goal to update; each record from your Nexset is sent as a JSON request body containing the fields to update.
Delete Goal
Delete a goal.
This endpoint deletes an existing goal. Provide the Goal ID of the goal to delete.
Create Time Off Request
Create a time off request.
This endpoint sends each record from your Nexset as a JSON request body to create a new time off request in your organization. The request body should contain the time off data in the format required by the ChartHop API.
Update Time Off Request
Update an existing time off request.
This endpoint updates an existing time off request. Provide the Time Off Request ID of the request to update; each record from your Nexset is sent as a JSON request body containing the fields to update.
Delete Time Off Request
Delete a time off request.
This endpoint deletes an existing time off request. Provide the Time Off Request ID of the request to delete.
ChartHop destinations can also be manually configured to send data to any valid ChartHop API endpoint. 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.
ChartHop APIs typically expect JSON format for most operations. For update and delete operations, include the ID of the object to be modified at the end of the URL.
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 send the data to the configured ChartHop endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the ChartHop endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
