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 Postings API

Job postings published to the company careers site.

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

This API exposes 2 JSON Schema definitions.

Tagged areas include Postings. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 2 JSON Schemas.

This API exposes 6 operations across 4 paths, and defines 3 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

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

6 operations 4 paths 3 schemas 4 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://api.lever.co/v1
Authentication
HTTP Basic, OAuth 2.0
Contact
Resource Areas
1

Authentication & Security 2

Lever Postings API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (BasicAuth). It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 22 scopes. By default, every request must be authenticated.

  • BasicAuth — HTTP Basic authentication using a Lever API key as the username and an empty password.

Paths & Operations 6

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

Postings 6

Job postings published to the company careers site.

GET
/postings
List Postings
listPostings 2 params → 200
POST
/postings
Create A Posting
createPosting body → 201
GET
/postings/{id}
Retrieve A Posting
getPosting 1 param → 200
PUT
/postings/{id}
Update A Posting
updatePosting 1 param → 200
GET
/{site}
List Public Postings
listPublicPostings 12 params → 200
GET
/{site}/{postingId}
Retrieve A Public Posting
getPublicPosting 2 params → 200

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Posting (12 properties), PostingCreate (4 properties), PostingList (3 properties). Each schema is shown below with its type and property counts.

Posting
object
12 properties
PostingCreate
object
4 properties 1 required
PostingList
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lever-co-postings-api-openapi.yml Raw ↑

Other APIs Lever publishes across the network.

Lever Postings XML Feed
Lever Webhooks
Lever Applications API
Lever Archive Reasons API
Lever Audit Events API
Lever EEO Responses API
Lever Feedback API
Lever Files API
Lever Interviews API
Lever Notes API
Lever Offers API
Lever Opportunities API
Where this information came from

This is an independent, third-party profile of Lever Postings 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.