The Lever Postings API is unauthenticated and publicly accessible; no API key is required for reading published postings
Send GET https://api.lever.co/v0/postings/{yourCompanyName}?mode=json to retrieve all published job postings as a JSON array
Use query parameters to filter results: team, department, location, commitment, and level are all supported; supply multiple values for the same parameter by repeating it, e.g., ?location=New+York&location=Austin
Paginate results using the skip and limit parameters; iterate until the returned array length is less than your requested limit
Each posting object includes an id, text (title), hostedUrl, applyUrl, categories (team, department, location, commitment), and content fields (description, lists) — map these to your job board schema
To fetch a single posting, send GET https://api.lever.co/v0/postings/{yourCompanyName}/{postingId}?mode=json
Known gotchas
The Postings API only exposes published (public) jobs; confidential or internal-only postings are not returned regardless of parameters
The company name segment in the URL is the Lever account slug, not a display name — confirm the exact slug with the account owner or from the Lever Settings page
This is the public-facing read API; creating or updating postings requires the authenticated Lever Data API with an API key and appropriate scopes
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp