> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking Lever as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/lever

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Adding a data source](#adding-a-data-source)
- [Available tables](#available-tables)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)

**Beta release**

This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do.

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

The Lever connector automatically pulls your Lever recruiting data into the PostHog data warehouse.

## Adding a data source

1.  Go to the [sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section in PostHog.
2.  Click **\+ New source** and then click **Link** next to Lever.
3.  You need a Lever API key. In your Lever account, go to **Settings → Integrations and API → API Credentials** and generate an API key. The key has full read access to your account's data, so no individual scopes need to be granted.
4.  Back in PostHog, enter the key in the `API key` field and click **Next**.
5.  Select the tables you want to sync, set the sync method and frequency, then click **Import**.

Once the syncs are complete, you can start using Lever data in PostHog.

## Available tables

| Table | Description | Sync method |
| --- | --- | --- |
| `opportunities` | Candidates and their opportunities in your pipeline | Incremental |
| `postings` | Job postings | Full refresh |
| `users` | Lever users in your account | Full refresh |
| `requisitions` | Hiring requisitions | Full refresh |
| `archive_reasons` | Reasons used when archiving opportunities | Full refresh |
| `stages` | Pipeline stages | Full refresh |
| `sources` | Candidate sources | Full refresh |
| `tags` | Tags applied to opportunities | Full refresh |

**Incremental** tables sync only new or updated records on each run. **Full refresh** tables reload all data on each sync.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `API key` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `opportunities` | A candidate's pipeline for a specific role — Lever's central record tying a person to an opening. | Incremental, Full refresh | createdAt, updatedAt | — |
| `applications` | A candidate's application to a job posting. Each opportunity has at most one application. | Full refresh | — | — |
| `offers` | An offer sent to a candidate for an opportunity, with its status and offer fields. | Full refresh | — | — |
| `interviews` | A scheduled interview for an opportunity, with its interviewers, time, and location. | Full refresh | — | — |
| `feedback` | A completed feedback form (scorecard) for an opportunity, usually submitted after an interview. | Full refresh | — | — |
| `postings` | A job posting (opening) in Lever that candidates can apply to. | Full refresh | — | — |
| `users` | A Lever user — a member of your hiring team. | Full refresh | — | — |
| `requisitions` | A requisition tracking approved headcount for a role in Lever. | Full refresh | — | — |
| `archive_reasons` | A reason a candidate's opportunity can be archived (e.g. hired, rejected). | Full refresh | — | — |
| `stages` | A stage in the Lever hiring pipeline that opportunities move through. | Full refresh | — | — |
| `sources` | A source through which candidates are added to Lever, keyed by its unique text value. | Full refresh | — | — |
| `tags` | A tag that can be applied to opportunities, keyed by its unique text value. | Full refresh | — | — |