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/stages to retrieve the list of pipeline stages and identify the target stage_id you want to move the opportunity to.
Identify the opportunity ID from your existing records or from a prior GET /v1/opportunities call.
Send PUT https://api.lever.co/v1/opportunities/:opportunity_id/stage with a JSON body containing the stage_id field set to the target stage's ID.
The response returns the updated opportunity object; verify the stage field reflects the new stage ID.
Optionally, add a note to the opportunity after the stage change with POST /v1/opportunities/:opportunity_id/notes to document the reason for the move.
If you need to trigger automated actions on stage change (e.g., sending an assessment), configure those in Lever's workflow settings rather than via API.
Known gotchas
Moving a Lever opportunity through the pipeline uses PUT /opportunities/:id/stage — not POST /addStage or any other method; using the wrong verb or path returns a 404 or 405.
You cannot move an archived opportunity back into an active stage via the stage endpoint alone; you must unarchive it first with PUT /opportunities/:id/archived setting archived to null.
Stage IDs are account-specific and change if stages are renamed or reordered; fetch them dynamically rather than hardcoding them.
Give your agent this knowledge — and 15,800+ more routes
One MCP install gives any agent live access to the full route map across 5,800+ 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?