Lever
Lever is a talent acquisition and applicant tracking platform built on the Opportunities data model. The Lever API exposes candidates, opportunities, postings, interviews, feedback, requisitions, users, files, webhooks, and a public Postings API for embedding job sites.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Lever the way a machine reads it — 60 machine-readable artifacts across 41 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Lever scores 52.3/100 (developing), with a separate agent-readiness read of 54/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Lever
Each block below is one kind of artifact we hold for Lever. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 41
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Lever Candidates API
Legacy Candidates endpoints maintained for backward compatibility. New integrations should use Opportunities; Candidates remain available for historical record retrieval.
Lever Contacts API
Contacts represent unique people across multiple opportunities, allowing Lever to deduplicate candidates who apply to multiple roles.
Lever Postings API
Manage job postings programmatically and power custom public job sites. The Postings API has a public read-only mode that does not require authentication for displaying job list...
Lever Applications API
Submit candidate applications against postings, including resumes, cover letters, and EEO survey data, and retrieve historical application records.
Lever Stages API
List the configured pipeline stages and disposition stages used to route opportunities through screening, interviews, offer, and hire.
Lever Archive Reasons API
Read archive reasons used when an opportunity is archived (rejected, hired, withdrawn) for downstream EEO and analytics reporting.
Lever Interviews API
Read interview events, panels, and schedules associated with an opportunity, including interviewer assignments and time slots.
Lever Feedback API
Read feedback forms and scorecards completed by interviewers and hiring managers, with templated and free-form fields.
Lever Feedback Templates API
Manage feedback form templates, including question definitions and scoring rubrics applied across postings and stages.
Lever Notes API
Add and retrieve free-form notes attached to opportunities for recruiter and hiring manager collaboration.
Lever Offers API
Read offer records associated with opportunities, including offer letters, approval status, and compensation breakdowns.
Lever Requisitions API
Manage requisitions backing each posting — headcount, compensation bands, and approval state — typically synced from an HRIS.
Lever Tags API
List and apply tags to opportunities for cohorting, sourcing, and reporting workflows.
Lever Sources API
Read source attribution (job board, referral, sourced) for opportunities to drive sourcing analytics.
Lever Files API
Upload and download files (resumes, cover letters, portfolio attachments) associated with opportunities; supports docx, doc, pdf, txt, jpg, png.
Lever Resumes API
Read parsed resume data — work history, education, skills — extracted from candidate submissions.
Lever Users API
Manage Lever users and their access roles (Super Admin, Admin, Team Member, Limited Team Member, Interviewer, Outsider).
Lever Audit Events API
Read tenant-scoped audit events for security monitoring and SOC reporting.
Lever EEO API
Read anonymous EEO survey data for compliance reporting; PII-isolated from the standard candidate endpoints.
Lever Webhooks API
Subscribe to Lever events (applicationCreated, candidateHired, stageChange, contactUpdate). Events are signed with HMAC-SHA256 for receiver verification.
Lever Postings Public API
The unauthenticated public Postings API for retrieving live job listings from a Lever account, used by external careers pages.
Lever XML Feed
XML feed of open postings used by job aggregators (Indeed, Glassdoor, LinkedIn) for syndication.
Lever Applications API
The Applications API from Lever — 2 operation(s) for applications.
Lever ArchiveReasons API
The ArchiveReasons API from Lever — 2 operation(s) for archivereasons.
Lever AuditEvents API
The AuditEvents API from Lever — 1 operation(s) for auditevents.
Lever Contacts API
The Contacts API from Lever — 1 operation(s) for contacts.
Lever EEO API
The EEO API from Lever — 2 operation(s) for eeo.
Lever Feedback API
The Feedback API from Lever — 2 operation(s) for feedback.
Lever Files API
The Files API from Lever — 2 operation(s) for files.
Lever Forms API
The Forms API from Lever — 2 operation(s) for forms.
Lever Interviews API
The Interviews API from Lever — 2 operation(s) for interviews.
Lever Notes API
The Notes API from Lever — 1 operation(s) for notes.
Lever Offers API
The Offers API from Lever — 1 operation(s) for offers.
Lever Opportunities API
The Opportunities API from Lever — 10 operation(s) for opportunities.
Lever Postings API
The Postings API from Lever — 5 operation(s) for postings.
Lever Requisitions API
The Requisitions API from Lever — 2 operation(s) for requisitions.
Lever Resumes API
The Resumes API from Lever — 1 operation(s) for resumes.
Lever Sources API
The Sources API from Lever — 1 operation(s) for sources.
Lever Stages API
The Stages API from Lever — 3 operation(s) for stages.
Lever Tags API
The Tags API from Lever — 1 operation(s) for tags.
Lever Users API
The Users API from Lever — 2 operation(s) for users.
Scroll within the panel for all 41 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Lever API
OPEN COLLECTIONGraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Lever GraphQL Schema
This document describes a conceptual GraphQL schema for the Lever ATS (Applicant Tracking System) API. Lever's production API is REST-based (https://api.lever.co/v1), but this s...
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Lever Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Lever Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Lever Finops
FINOPSFeatures 9
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Scroll within the panel for all 9 ·
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Lever — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/lever · machine-readable index on apis.io