# Lever Job Postings API

> Open jobs of any company hiring on Lever, filterable by location, team and commitment

- Vendor: `leverjobpostingsapi` · version 1.0 · category Jobs · tags lever api, job postings api, job board api, careers page api, open jobs api, hiring data api
- Datasource: custom HTTP routes
- Marketplace page: https://apiclay.com/api/leverjobpostingsapi
- This document: https://apiclay.com/docs/leverjobpostingsapi.md
- OpenAPI 3.1: https://apiclay.com/api/leverjobpostingsapi/openapi.json
- MCP: connect https://api.apiclay.com/v1/mcp (see https://apiclay.com/llms.txt), then `apiclay_describe_api` with vendor `leverjobpostingsapi`
- Updated: 2026-11-18

## About

## Lever Job Postings API

Read the open jobs of any company that hires through Lever, with title, team, department, location, commitment, workplace type, full description (HTML and plain text) and apply URL.

Data comes from **lever.co** (https://jobs.lever.co). Every route calls the source's own public JSON endpoint (found with the live-URL scan of https://jobs.lever.co) and returns it unchanged.

Typical flow: take the company slug from its careers URL (`jobs.lever.co/palantir` -&gt; `palantir`) and call `/postings`; use `limit`/`skip` to page.

### Routes

#### GET `/postings` - Postings of a company
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| company | path | string | yes | Lever site name, e.g. `palantir`. |
| limit | query | number | no | Postings per call. |
| skip | query | number | no | Postings to skip. |
| location | query | string | no | Exact location name. |
| commitment | query | string | no | e.g. `Full-time`. |
| team | query | string | no | Team name. |
| department | query | string | no | Department name. |
| level | query | string | no | Level name. |

Returns: `[{id, text, categories{location, team, department, commitment}, country, workplaceType, createdAt, descriptionPlain, lists[], hostedUrl, applyUrl}]`.

#### GET `/posting` - Posting details
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| company | path | string | yes | Lever site name. |
| posting_id | path | string | yes | `id` from `/postings`. |

Returns: one posting with the fields above.

### Caveats

- Descriptions make each posting 10-15 KB; use `limit`.
- Upstream responses can change over time. Verify fields before relying on them.
- Not affiliated with or endorsed by lever.co.

## Pricing

- Pay as you go: 0.0012 credits/request
- Trial: 1 free requests per buyer
- Billing order: trial requests -> subscribed plan requests -> pay as you go. 1 credit's USD value is shown on the marketplace page.

## HTTP routes

Only the public, buyer-facing parts of each route are listed; vendor-side credentials stay on the gateway.

### GET /postings — Postings of a company
- Gateway: `GET https://api.apiclay.com/v1/api/leverjobpostingsapi/postings`
- Public query params: `limit` (number), `skip` (number), `location` (string), `commitment` (string), `team` (string), `department` (string), `level` (string), `company` (string, required)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### GET /posting — Posting details
- Gateway: `GET https://api.apiclay.com/v1/api/leverjobpostingsapi/posting`
- Public query params: `company` (string, required), `posting_id` (string, required)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

## Call example

```bash
curl -X GET "https://api.apiclay.com/v1/api/leverjobpostingsapi/postings?company=<company>" \
  -H "token: <YOUR_APICLAY_TOKEN>"
```

Index of every published API: https://apiclay.com/llms.txt
