> For the complete documentation index, see [llms.txt](https://integrations.drivetrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.drivetrain.ai/integration-guide/readme/hris-and-ats/integrating-with-lattice.md).

# Integrating with Lattice

Sync people data from Lattice into Drivetrain automatically. Connect your performance management tool and keep all headcount models current over time.

[Prerequisites](#prerequisites)

[Lattice Setup](#lattice-setup)\
[Generate API Key](#generate-api-key)

## Prerequisites

To connect Lattice to Drivetrain, you need:

* An active Lattice account
* Super Admin privileges on Lattice
* Admin privileges in Drivetrain

## Lattice Setup <a href="#lattice-setup" id="lattice-setup"></a>

Drivetrain supports integration with Lattice via **API** using an API key.

### Generate API key <a href="#generate-api-key" id="generate-api-key"></a>

{% hint style="info" %}
Ensure that the person creating the API key is a super admin in your Lattice account.
{% endhint %}

1. Log in to your Lattice account.
2. On the left-hand navigation pane, select **Admin** > **Settings** > **API Keys**.
3. Click **Generate API key**.
4. Make a note of the API key in a secured document.

{% hint style="info" %}
That’s it! Share the API key with your customer success manager so that they can get started!
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://integrations.drivetrain.ai/integration-guide/readme/hris-and-ats/integrating-with-lattice.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.