Lever API

Name: Lever API
Brand: Lever API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHR recruitingRecruiting Atsbasic, bearer53 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the Lever API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Lever API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Lever API.

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

GET STARTED

Start building with Lever API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Lever API for, with concrete tasks.

★ 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.

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.

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.

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.

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

Key Endpoints

53 endpoints — jentic publishes the only available openapi specification for lever api, keeping it validated and agent-ready.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Lever API keys and OAuth Bearer tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw API keys never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'advance candidate to next interview stage') and Jentic returns matching Lever operations with their input schemas, so the agent can call the right endpoint without reading Lever's documentation.

Time to first call

Direct Lever integration: 2-4 days for auth setup, pagination handling, and webhook configuration. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Lever API through Jentic.

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 at https://app.jentic.com/sign-up.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up.

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.

Lever API

Connect the Lever API to your agent

Capabilities

Start building with Lever API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs