Lattice

Lattice is a comprehensive people management platform that provides tools for performance management, employee engagement, and career development, helping organizations build high-performing teams through continuous feedback, goal setting, and employee growth tracking capabilities.

Power end-to-end data operations for your Lattice API with Nexla. Our bi-directional Lattice connector is purpose-built for Lattice, 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 Lattice or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Lattice 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

Prerequisites

Before creating a Lattice credential, you need to obtain an API Key from your Lattice admin dashboard. The API Key is required to authenticate with the Lattice API.

To obtain your API Key, sign in to your Lattice account with administrator permissions and navigate to the admin dashboard. In the admin dashboard, locate the API Settings or API Keys section where you can view and manage your API keys. You can generate a new API Key or use an existing one. If you're generating a new API Key, you may be asked to provide a name or description for the key to help identify it later. Copy the API Key immediately after generation, as it may not be displayed again for security reasons. Store the API Key securely, as you will need it to configure your Nexla credential.

The API Key is sent in the Authorization header with the Bearer prefix (e.g., Authorization: Bearer {api_key}) for all API requests to the Lattice API. The API Key authenticates your account and grants access to your Lattice data, including users, departments, feedback, goals, review cycles, and tags. For detailed information about API key setup, authentication, and available API endpoints, refer to the Lattice API reference and Lattice API authentication documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key	Yes	Yes	Enter your Lattice API Key. You can view and manage your API keys in the Lattice admin dashboard.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Lattice

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

3. Enter your Lattice API Key in the API Key field. This is the API Key you obtained from your Lattice admin dashboard. The API Key is sent in the Authorization header with the Bearer prefix (e.g., Authorization: Bearer {api_key}) for all API requests to the Lattice API. The API Key authenticates your account and determines what data and operations you can access based on your account permissions.

   Keep your API Key secure and do not share it publicly. The API Key provides access to your Lattice account data and should be treated as sensitive information. If your API Key is compromised, you should immediately regenerate it in your Lattice admin dashboard. You can view and manage API keys in your Lattice admin dashboard (API Settings or API Keys section). The API Key is sent in the Authorization: Bearer {api_key} header for all API requests to the Lattice API. The API Key does not expire automatically, but you can regenerate it at any time if needed. For detailed information about obtaining and managing API keys, API authentication, and available endpoints, see the Lattice API reference and Lattice API authentication documentation.

4. 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.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Lattice connector tile, then select the credential that will be used to connect to the Lattice account, and click Next; or, create a new Lattice credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Lattice endpoints. Each template is designed specifically for the corresponding Lattice endpoint, making data source setup easy and efficient. 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.

Fetch Object Lists

Fetch Object Lists

• Select the type of Lattice API object you wish to fetch from the Object Type pulldown menu. Available object types include: Departments, Feedbacks, Goals, Review Cycles, Tags, and Users. The default value is "users".
• The endpoint uses GET requests to https://api.latticehq.com/v1/{object_name}?limit=100 where {object_name} is the object type you selected. The endpoint URL is automatically constructed based on your selection.
• The endpoint uses pagination (iteration.type: paging.next.token) to retrieve all objects. Pagination uses the startingAfter query parameter with a cursor token to navigate through pages. The limit parameter is set to 100 records per page. The endpoint will automatically fetch all pages until all objects are retrieved.
• The response data path is $.data[*], which extracts all object records from the data array in the API response. The pagination cursor is extracted from $.endingCursor for the next page token.
• The date format is yyyy-MM-dd with a time unit of dd (days), which is used for incremental data extraction based on record dates.

This endpoint retrieves a list of all objects of the selected type from your Lattice account. The endpoint requires API Key authentication, which is handled automatically by your credential configuration. The API Key is sent in the Authorization: Bearer {api_key} header for all API requests. The endpoint supports pagination through cursor-based pagination using the startingAfter parameter, which allows you to retrieve large lists of objects efficiently. For detailed information about fetching object lists, pagination, and available object types, see the Lattice API reference.

Fetch One Record

Fetch One Record

• Select the type of Lattice API object you wish to fetch from the Object Type pulldown menu. Available object types include: Department, Feedback, Goal, Question, Reviewee, Task, and User. The default value is "user".
• Enter the ID of the specific object you wish to fetch in the Record ID field. This is the unique identifier for the object in your Lattice account. You can obtain record IDs from the "Fetch Object Lists" endpoint or from your Lattice account dashboard.
• The endpoint uses GET requests to https://api.latticehq.com/v1/{object_name}/{record_id} where {object_name} is the object type you selected and {record_id} is the Record ID you specified. The endpoint URL is automatically constructed based on your selections.
• The endpoint does not use pagination (iteration.type: static.url), so it will fetch a single record per execution. The response data path is $, which extracts the entire response object.
• The date format is yyyy-MM-dd with a time unit of dd (days), which is used for incremental data extraction based on record dates.

This endpoint retrieves a specific record of the selected type from your Lattice account. The endpoint requires API Key authentication, which is handled automatically by your credential configuration. The API Key is sent in the Authorization: Bearer {api_key} header for all API requests. The Record ID identifies which specific object to retrieve. For detailed information about fetching individual records and available object types, see the Lattice API reference.

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.

Manual configuration

Lattice data sources can also be manually configured to ingest data from any valid Lattice API endpoint, including endpoints not covered by the pre-built templates or when custom query parameters, HTTP methods, or data transformations are needed. 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. Lattice API endpoints typically follow the pattern https://api.latticehq.com/v1/{endpoint_path}.

Ensure the API endpoint URL is correct and accessible with your current credentials. You can test the endpoint using the Test button after configuring the URL. The endpoint requires API Key authentication, which is handled automatically by your credential configuration. The API Key is sent in the Authorization: Bearer {api_key} header for all API requests. For detailed information about Lattice API endpoints, authentication, and available APIs, see the Lattice API reference.

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 Lattice 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.