lever.posting

stable Standard

One Lever posting by id.

GET /v1/lever/posting

What you get#

One Lever record in Onekey's unified shape, in data. If the record does not exist you get a 404 not_found and are not charged.

What it costs#

Standard · 1 credit for a fresh fetch, charged only when it succeeds.
Free when served from cache (0.2 credit for a cached response over 100 KB).
Free if the request is invalid (never charged) or the source fails or reports not found (refunded).

Parameters#

Name	Type	Required	Default	What it is	Constraints
`company`	string	yes	(required)	Lever company slug	max 63 chars; must match `[A-Za-z0-9][A-Za-z0-9_-]{0,62}`; trimmed, lowercased
`posting_id`	string	yes	(required)	Lever posting UUID	max 36 chars; must match `[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}`; trimmed, lowercased

Request#

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

Try it

Add your key to run this call right here. No key? Get one free. The key stays in this tab.

Recorded response#

A real Lever response, recorded and returned in Onekey's shape. Fields the platform does not provide are null.

json

{
  "success": true,
  "data": {
    "content": {
      "id": "2193db3f-77c5-43b8-b030-8f92c9882bf1",
      "title": "Android Engineer - Experience",
      "url": "https://jobs.lever.co/spotify/2193db3f-77c5-43b8-b030-8f92c9882bf1",
      "createdAt": "2026-06-23T11:29:45Z",
      "text": "We design Spotify’s consumer experience—end to end, moment to moment, across every screen, platform, and partner integration. Our mission is to make listening feel effortless, personal, and joyful for billions of users around the world. That means turning complexity into clarity across hundreds of touchpoints—from our mobile and desktop apps to the smart speakers, TVs, cars, and integrations where Spotify shows up every day. If it touches a consumer, we shape it. We bring deep insight into human behavior, design, and technology to craft experiences that feel intuitive, expressive, and unmistakably Spotify.\nThe Stream Reporting team is responsible for capturing and processing the consumption signals that power some of Spotify’s most important experiences and business functions. Our systems help ensure accurate royalty reporting, support experimentation and analytics, and provide trusted data that informs recommendations and personalization across Spotify.\nWe’re looking for an Android Engineer to join a highly collaborative team working at the intersection of mobile development, data, and platform systems. This is an opportunity to build software that operates at Spotify scale and helps power experiences used by millions of listeners every day. You’ll help shape how listening and engagement signals are captured across Spotify’s mobile experiences and transformed into trusted datasets used throughout the company.\n \n"
    },
    "listing": {
      "applyUrl": "https://jobs.lever.co/spotify/2193db3f-77c5-43b8-b030-8f92c9882bf1/apply",
      "jobType": "Permanent"
    },
    "entity": {
      "location": "London",
      "country": "GB"
    },
    "ext": {
      "department": "Engineering",
      "team": "Experience",
      "workplaceType": "hybrid"
    }
  },
  "metadata": {
    "platform": "lever",
    "endpoint": "posting",
    "cached": false,
    "stale": false,
    "age_s": 0,
    "fetched_at": "2026-01-01T12:00:00+00:00",
    "credits_charged": 1,
    "request_id": "7f3a9c2e5b1d4c8fa2e6d0b9c4f18e37"
  },
  "error": null
}

Field mapping#

How this endpoint's source fields become Onekey's unified schema. Fields the source lacks come back as null.

Source path	Onekey field	Transform
`id`	`content.id`	-
`text`	`content.title`	-
`hostedUrl`	`content.url`	`safeUrl`
`createdAt`	`content.createdAt`	`toIsoDate`
`descriptionPlain`	`content.text`	-
`applyUrl`	`listing.applyUrl`	`safeUrl`
`categories.location`	`entity.location`	-
`categories.department`	`ext.department`	-
`categories.team`	`ext.team`	-
`categories.commitment`	`listing.jobType`	-
`workplaceType`	`ext.workplaceType`	-
`country`	`entity.country`	-

Caching and freshness#

Fresh for about 30 minutes. Repeat calls in that window are served from cache and are free.
Between 30 minutes and 6 hours the cached copy is still served instantly and marked stale: true while Onekey refreshes it in the background.
If the source is down when a refresh is needed, the last copy can be served for up to 1 day more (marked stale).
A "not found" is remembered for 5 minutes and is free.
The cache is shared across all customers, which is what keeps repeat calls cheap.

What can go wrong#

Status	Code	What to do
401	`unauthorized`	Check the `x-api-key` header.
402	`insufficient_credits`	Add credits; your balance must cover the price.
404	`not_found`	That record does not exist. Free; do not retry.
422	`invalid_params`	Fix the parameters using the table above. Free.
429	`rate_limited`	Wait `Retry-After` seconds, then retry.
502	`upstream_error`	The source failed. Refunded; retry with backoff.

See Errors for the full list and retry guidance.

Status: stable (verified against the live source).