Create and manage Lever requisitions linked to job postings
domain: lever.co · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
GET https://api.lever.co/v1/requisitions to list existing requisitions and understand the fields in use (requisition_code, hiring_manager, department, headcount).
POST to https://api.lever.co/v1/requisitions with a body containing requisition_code, name, headcount_total, and any custom fields defined in your Lever account.
To link a requisition to a posting, POST to https://api.lever.co/v1/postings/:posting_id/requisitions/:requisition_id; this associates the open headcount with the job.
Monitor requisition fill status by comparing headcount_hired against headcount_total using the requisition object; Lever updates headcount_hired as offers are accepted.
To remove a requisition from a posting, DELETE /v1/postings/:posting_id/requisitions/:requisition_id.
Pull requisition reports by filtering opportunities with the requisition_id query parameter on GET /v1/opportunities.
Known gotchas
Requisition custom fields must be configured in Lever settings before they can be set via API; sending unknown field keys returns a validation error.
A posting can be linked to multiple requisitions; ensure your headcount tracking aggregates across all linked requisitions rather than assuming a one-to-one relationship.
Headcount_hired is calculated by Lever based on accepted offers — do not attempt to set this field directly via the API.
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?