> 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-sapling.md).

# Integrating with Sapling

Link Sapling to Drivetrain and pull employee records into planning models automatically. Covers authorization and the permissions you need.

[Prerequisites](#prerequisites)

[Sapling Setup](#sapling-setup)\
[Locating and Generating New API Keys](#locating-and-generating-new-api-keys)

## Prerequisites

To connect Sapling to Drivetrain, you need:

* An active Sapling account
* Super-Admin privileges on Sapling
* Admin privileges in Drivetrain

## Sapling Setup <a href="#sapling-setup" id="sapling-setup"></a>

Drivetrain supports in-built integration with Sapling. You would need to generate and enter API Keys from an account with administrator access to get started.

### Locating and Generating New API Keys <a href="#locating-and-generating-new-api-keys" id="locating-and-generating-new-api-keys"></a>

Users with Super Admin permissions can generate and view their own API keys.

1. Go to the **Integrations** page of your Sapling account
2. Navigate to the **API Keys** tab
3. Copy an existing API key, or click on the **Create New Key** button
4. Be sure to name your key descriptively, so you know how each application uses that key

{% hint style="danger" %}
API Key expires in 90 days.

The keys don’t get automatically renewed for security reasons, however, an email is sent to the owner of the API key 7 days before its expiration.
{% endhint %}

{% hint style="info" %}
That’s it! Inform your Drivetrain 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-sapling.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.