# Lever on Onekey

> 2 endpoints for Lever (2 stable, 0 beta), 1 to 5 credits each. Category: Jobs & professional. One key, one JSON shape.

Base URL: https://api.onekey.dev
Auth: header `x-api-key: <key>`. Call shape: `GET /v1/{platform}/{endpoint}?{params}`.
Every response is `{success, data, metadata, error}`; check `success` first. Cost is in `metadata.credits_charged`. Free when served from cache (0.2 credit for a cached response over 100 KB). Failed and not-found calls are refunded.
Status: stable = verified against the live source; beta = not yet verified, fields may be missing.

Page: https://onekey.dev/platforms/lever
Reference (Markdown): https://onekey.dev/docs/api/lever.md
All docs: https://onekey.dev/llms.txt

## Canonical fields returned

Unified-schema fields (same names on every platform), with how many of the 2 mapped Lever endpoints return each:

- `content.createdAt` (ISO 8601 date): 2
- `content.id` (string): 2
- `content.text` (string): 2
- `content.title` (string): 2
- `content.url` (URL): 2
- `entity.country` (string): 2
- `entity.location` (string): 2
- `listing.applyUrl` (URL): 2
- `listing.jobType` (string): 2
- plus 3 platform-specific fields under `ext.`

## Endpoints

### lever.posting

One Lever posting by id.
- Price: 1 credit per fresh call. Status: stable. Returns: one record.
- Request: `GET https://api.onekey.dev/v1/lever/posting?company=spotify&posting_id=2a55d6c9-c564-443a-be3e-a3851db5a93b` with header `x-api-key: YOUR_API_KEY`
- Parameters:
  - `company` (string, required): Lever company slug
  - `posting_id` (string, required): Lever posting UUID
- Fields returned: `content.id`, `content.title`, `content.url`, `content.createdAt`, `content.text`, `listing.applyUrl`, `entity.location`, `listing.jobType`, `entity.country`, `ext.department`, `ext.team`, `ext.workplaceType`
- Reference: https://onekey.dev/docs/api/lever/posting.md

### lever.postings

List open postings of a company on Lever.
- Price: 5 credits per fresh call. Status: stable. Returns: a list.
- Request: `GET https://api.onekey.dev/v1/lever/postings?company=spotify` with header `x-api-key: YOUR_API_KEY`
- Parameters:
  - `company` (string, required): Lever company slug, e.g. spotify
- Fields returned: `content.id`, `content.title`, `content.url`, `content.createdAt`, `content.text`, `listing.applyUrl`, `entity.location`, `listing.jobType`, `entity.country`, `ext.department`, `ext.team`, `ext.workplaceType`
- Reference: https://onekey.dev/docs/api/lever/postings.md

## Sample request

```bash
curl "https://api.onekey.dev/v1/lever/posting?company=spotify&posting_id=2a55d6c9-c564-443a-be3e-a3851db5a93b" \
  -H "x-api-key: YOUR_API_KEY"
```