How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Lever Requisitions API

Manage requisitions backing each posting — headcount, compensation bands, and approval state — typically synced from an HRIS.

Lever Requisitions API is one of 24 APIs that Lever publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Requisitions and Headcount. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 5 operations across 2 paths. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://api.lever.co/v1.

5 operations 2 paths 0 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Server
https://api.lever.co/v1
Authentication
HTTP Basic, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Lever Requisitions API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • basicAuth — API key supplied as the basic auth username with empty password.
  • bearerAuth — OAuth 2.0 bearer access token (Lever Partner OAuth apps).

Paths & Operations 5

Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Requisitions 5
GET
/requisitions
List requisitions
getRequisitions → 200
POST
/requisitions
Create requisition
postRequisitions body → 201
GET
/requisitions/{requisition}
Retrieve requisition
getRequisitionsByRequisition 1 param → 200
PUT
/requisitions/{requisition}
Update requisition
putRequisitionsByRequisition 1 param body → 200
DELETE
/requisitions/{requisition}
Delete requisition
deleteRequisitionsByRequisition 1 param → 204

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lever-requisitions-api-openapi.yml Raw ↑

Other APIs Lever publishes across the network.

Lever Candidates API
Lever Feedback Templates API
Lever Webhooks API
Lever Postings Public API
Lever XML Feed
Lever Applications API
Lever Contacts API
Lever EEO API
Lever Feedback API
Lever Files API
Lever Forms API
Lever Interviews API
Where this information came from

This is an independent, third-party profile of Lever Requisitions API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.