To add a note, POST to https://api.lever.co/v1/opportunities/:opportunity_id/notes with a JSON body containing a value field (the note text) and optional fields such as secret (boolean, makes note visible only to admins) and score (integer rating).
The response returns the created note object with an id, createdAt timestamp, and the author's user information.
To list existing notes, GET https://api.lever.co/v1/opportunities/:opportunity_id/notes; paginate with cursor tokens if there are many notes.
To filter notes by type, use the type query parameter; valid values include 'note', 'called', 'emailed', and others depending on your account configuration.
Notes cannot be edited after creation; if a note is incorrect, add a corrective note and optionally delete the original with DELETE /v1/opportunities/:opportunity_id/notes/:note_id.
Use the perform_as query parameter with a Lever user ID to attribute the note to a specific user rather than the API key owner.
Known gotchas
The perform_as query parameter is required if you want the note attributed to the actual recruiter rather than the system API user; omitting it attributes all notes to the API key's associated user.
Secret notes are only visible to users with admin permissions in Lever; do not use secret=true for notes that interviewers need to see.
The note value field does not support rich HTML — it is plain text only; any HTML tags will appear as literal characters in the Lever UI.
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