> 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/integrate-with-drivetrain/hris-and-ats/integrating-with-lever.md).

# Integrating with Lever

[Prerequisites](#prerequisites)

[Lever Setup](#lever-setup)

## Prerequisites

To connect Lever to Drivetrain, you need:

* An active Lever account
* Super admin privileges on Lever

### Lever Setup <a href="#lever-setup" id="lever-setup"></a>

1. Log into your Lever account, navigate to **Settings > Integrations** by clicking on the top left drop-down menu.

<figure><img src="/files/yPuFSYlPch7YmWYHWOXK" alt=""><figcaption></figcaption></figure>

2. Navigate to the API credentials tab. Under Lever API credentials, click **Generate New Key**.

<figure><img src="/files/WmzzjaQN1r8sgyB0rgOw" alt=""><figcaption></figcaption></figure>

3. Make a note of the API key.
4. Under **Permissions**, choose the **Select all read** preset.

<figure><img src="/files/ExCWXwAMRLY3Gp4c13Un" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
That’s it! Share the API Key with your customer success manager so 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.