canonical: https://jentic.com/apis/lever.co/lever

# Lever API

Jentic publishes the only available OpenAPI specification for Lever API, keeping it validated and agent-ready. Track candidates through hiring pipelines with 53 endpoints covering opportunities, postings, interviews, offers, and feedback collection. Manage the full recruiting lifecycle from job posting through offer letter with structured access to candidate profiles, interview panels, referral sources, and requisition tracking.

## For AI agents

Search opportunities, advance candidates through pipeline stages, schedule interviews, and retrieve hiring analytics from a Lever recruiting account.

## Scope

Does not handle employee onboarding, payroll, performance reviews, or HRIS functions - use for recruiting and applicant tracking only.

## Capabilities

- Search and filter candidate opportunities by stage, source, or posting
- Advance or archive candidates through configurable pipeline stages
- Attach interview feedback, scorecards, and notes to candidate profiles
- Post and manage job listings with requisition-linked approval workflows
- Schedule interview panels and retrieve interviewer availability
- Track referral sources and attribute hires to recruiting channels
- Export offer details including compensation, start date, and approval status

## Use cases

### AI Agent Recruiting Automation

AI agents use the Lever API through Jentic to automate recruiting workflows without direct Lever credentials. An agent searches for 'advance candidate to next stage', loads the schema for the stage transition endpoint, and moves qualified candidates forward. Combined with the feedback endpoint, agents can summarize interview notes and flag candidates ready for offer.

Example prompt: List all opportunities in the 'Phone Screen' stage for posting ID P001, then advance the top-rated candidate to 'On-Site Interview'

### Candidate Pipeline Reporting

Pull real-time pipeline metrics across all postings to feed recruiting dashboards and hiring forecasts. The opportunities endpoint supports filtering by stage, posting, creation date, and tags, enabling time-to-hire calculations, stage conversion rates, and bottleneck identification without manual data exports from the Lever UI.

Example prompt: Retrieve all opportunities created in the last 30 days grouped by stage and return the count at each stage for posting ID P001

### Interview Coordination

Coordinate interview scheduling by accessing panel assignments, interviewer details, and feedback submissions for each opportunity. The interviews sub-resource tracks scheduled, completed, and cancelled interviews with timestamps and participant lists. Integrations connect Lever with calendar tools and video conferencing platforms to streamline the scheduling workflow.

Example prompt: Retrieve all scheduled interviews for opportunity ID O001 and return the interviewer names, dates, and whether feedback has been submitted

### Job Posting Management

Programmatically create, update, and close job postings with linked requisitions. The postings endpoint supports full lifecycle management including publishing to job boards, setting application forms, and tracking requisition approval status. Teams use this to sync postings across multiple platforms from a single source of truth in Lever.

Example prompt: Create a new job posting for 'Senior Backend Engineer' linked to requisition ID R001 with the Engineering department tag

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /opportunities | List all candidate opportunities |
| GET | /opportunities/{id} | Get a specific opportunity |
| POST | /opportunities/{opportunityId}/stage | Advance candidate to a stage |
| GET | /opportunities/{opportunityId}/interviews | List interviews for an opportunity |
| GET | /opportunities/{opportunityId}/feedback | Get feedback for an opportunity |
| GET | /postings | List all job postings |
| GET | /opportunities/{opportunityId}/offers | Get offers for an opportunity |
| POST | /opportunities/{opportunityId}/notes | Add a note to an opportunity |

## Key resources

- **Opportunities** — Candidate records with applications, interviews, notes, offers, feedback, and stage tracking
- **Postings** — Job listings with requisition links, application forms, and publishing status
- **Stages** — Pipeline stage definitions and ordering for candidate progression
- **Users** — Lever account users including recruiters, hiring managers, and interviewers
- **Requisitions** — Headcount requisitions with approval workflows and posting associations

## Why Jentic

- **Setup:** Wiring the Lever API by hand means supporting both HTTP Basic with the API key as username and OAuth bearer tokens, learning which endpoints cover opportunities, interviews, and offers, and calling api.lever.co yourself. Through Jentic you install once, import the Lever API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Lever puts the opportunity id in the URL path (/opportunities/{opportunityId}/stage, /notes, /offers), so a rule can pin your agent to one opportunity: it can read feedback and interviews and add notes there. You choose the operations it may call, so stage changes are not included unless you add them.
- **Credential handling:** Your Lever API key or OAuth token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'advance a candidate to the next interview stage' or 'list open postings', and Jentic returns the matching Lever operation with its input schema so the agent calls the right endpoint without browsing the Lever docs.

## Related APIs

- **Greenhouse Harvest API** — Enterprise ATS with structured candidate data, scorecards, and department-level reporting
- **SmartRecruiters API** — Enterprise hiring platform with marketplace integrations and AI-powered candidate matching
- **Ashby API** — Modern ATS with built-in analytics, scheduling, and CRM for high-growth companies
- **BambooHR API** — Full HRIS platform for employee records, onboarding, and time-off management

## FAQ

### Why is there no official OpenAPI spec for Lever API?

Lever does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Lever API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Lever API use?

The API supports HTTP Basic authentication (API key as username, no password) and OAuth 2.0 Bearer tokens for production integrations. Basic auth is suitable for internal tools while Bearer tokens are required for partner integrations. Through Jentic, API keys are stored in your Jentic One instance and agents authenticate without handling raw credentials.

### Can I advance a candidate through pipeline stages with the Lever API?

Yes. Use POST /opportunities/{opportunityId}/stage with the target stage ID in the request body to move a candidate forward or backward in the pipeline. First retrieve available stages via GET /stages to identify valid stage IDs for the transition.

### What are the rate limits for the Lever API?

Lever enforces rate limits of 10 requests per second for most endpoints. Batch list endpoints like GET /opportunities support pagination with limit and offset parameters (max 100 per page). The API returns HTTP 429 when limits are exceeded with a Retry-After header.

### How do I retrieve candidate interview feedback through Jentic?

Search Jentic for 'get interview feedback for candidate', load the schema for GET /opportunities/{opportunityId}/feedback, and execute with the opportunity ID. The response includes feedback forms, ratings, and interviewer comments. Install with pip install jentic and authenticate through Jentic One, the self-hosted execution layer.

### Does the Lever API support webhooks for real-time hiring events?

Yes. The Webhooks resource allows registering callback URLs for events including new applications, stage changes, offer extensions, and candidate archives. This enables real-time integrations with Slack notifications, onboarding systems, and HRIS platforms without polling the opportunities endpoint.

### Can I limit what my agent is allowed to do with the Lever API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Lever operations and credentials the agent may use. Because Lever puts the opportunity id in the URL path, such as /opportunities/{opportunityId}/stage, /opportunities/{opportunityId}/notes, and /opportunities/{opportunityId}/offers, you can pin the agent to a single opportunity and let it read feedback and interviews and add notes there. You choose exactly which operations it may call, so stage changes stay off limits unless you explicitly allow them.