Lever
Bring new starters, changes and leavers from Lever into every system that needs them, with HR approving each change.
34 ways to read, 12 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Lever, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Add noteApproval by rule
- Create opportunityApproval by rule
- List applicationsRead
Example flow
- Lever · List applicationsDone
- Lever · Add noteNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Lever.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Lever
- Lever's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.
For developers
Technical detail
Read and write Lever opportunities, contacts, notes, postings and requisitions, and read applications, feedback, interviews, panels, forms, files, offers and settings.
Employ Inc. API docs- Source actions
- 34
- Destination actions
- 12
- Data types
- 29
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Applications2
- Get applicationSource
One application on an opportunity.
- List applicationsSource
Applications on an opportunity with posting, type and archive state (IP address and browser data are not returned).
Archive reasons2
- Get archive reasonSource
One archive reason by ID.
- List archive reasonsSource
Archive reasons, including hired reasons.
Contacts2
- Get contactSource
One contact by ID.
- Update contactDestinationProvider duplicate protectionApproval before production
Updates a candidate contact's name, headline, location, emails or phones.
Deleted opportunities1
- List deleted opportunitiesSourceIncremental
Opportunities deleted in Lever, optionally since a timestamp, for sync clean-up.
Feedback templates1
- List feedback templatesSource
Interview feedback templates with their question fields.
Feedback2
- Get feedbackSource
One feedback on an opportunity.
- List feedbackSource
Interview feedback forms on an opportunity with their field values.
File actions1
- List file activitySourceIncremental
File uploads, imports and removals on an opportunity, optionally since a time.
Files1
- List filesSource
File metadata on an opportunity (download links are not returned).
Form templates1
- List profile form templatesSource
Profile form templates with their question fields.
Forms1
- List profile formsSource
Completed profile forms on an opportunity; currency and pay questions are omitted.
Interviews2
- Get interviewSource
One interview on an opportunity.
- List interviewsSource
Scheduled interviews on an opportunity.
Notes4
- Add noteDestinationNot retried automaticallyApproval before production
Adds a note (or a comment to an existing note) on an opportunity.
- Get noteSource
One note on an opportunity.
- List notesSource
Notes on an opportunity with comment threads.
- Update noteDestinationProvider duplicate protectionApproval before production
Replaces the text of a note that was created through the API.
Offers1
- List offersSource
Offers on an opportunity (read-only; offer fields with compensation are not returned).
Opportunities3
- Create opportunityDestinationNot retried automaticallyApproval before production
Creates a candidate opportunity, optionally applied to one posting and placed in a stage.
- Get opportunitySource
One opportunity with stage, tags, sources and consent status.
- List opportunitiesSourceIncremental
Pipeline opportunities, optionally changed since a timestamp or filtered by stage, posting or tag.
Opportunity archive1
- Archive or restore opportunityDestinationProvider duplicate protectionApproval before production
Archives an opportunity with a reason (optionally hiring against a requisition), or restores it when no reason is given.
Opportunity links1
- Update opportunity linksDestinationProvider duplicate protectionApproval before production
Adds or removes links on an opportunity.
Opportunity sources1
- Update opportunity sourcesDestinationProvider duplicate protectionApproval before production
Adds or removes sources on an opportunity.
Opportunity stage1
- Change opportunity stageDestinationProvider duplicate protectionApproval before production
Moves an opportunity to a pipeline stage.
Opportunity tags1
- Update opportunity tagsDestinationProvider duplicate protectionApproval before production
Adds or removes tags on an opportunity.
Panels1
- List interview panelsSource
Interview panels on an opportunity with times, stage and interviews.
Postings4
- Create postingDestinationNot retried automaticallyApproval before production
Creates a job posting (draft by default). Salary ranges are never set.
- Get postingSource
One posting with its content.
- List postingsSourceIncremental
Job postings with state, team, department, location and owners.
- Update postingDestinationProvider duplicate protectionApproval before production
Partially updates a posting's title, state, categories, tags, content or workplace type. Salary ranges are never changed.
Referrals1
- List referralsSource
Referral forms on an opportunity with referrer and answers; currency and pay questions are omitted.
Requisition fields1
- List requisition fieldsSource
Custom requisition field definitions. Fields whose names indicate pay or compensation are omitted.
Requisitions3
- Create requisitionDestinationNot retried automaticallyApproval before production
Creates a requisition from an HRIS position. A compensation band is never sent.
- Get requisitionSource
One requisition by ID.
- List requisitionsSource
Requisitions with headcount, status, owner and hiring manager (compensation bands omitted).
Resumes1
- List resumesSource
Resumes on an opportunity with file metadata and parsed positions and schools.
Sources1
- List sourcesSource
Candidate sources with usage counts.
Stages2
- Get stageSource
One stage by ID.
- List stagesSource
Pipeline stages in order.
Tags1
- List tagsSource
Candidate tags with usage counts.
Users2
- Get userSource
One user by ID.
- List usersSource
Lever users with access role (use their IDs as perform-as users and owners).
Access and limits
- Authentication
- Lever API key (HTTP Basic, empty password)
- Plans and access
- API keys are available to Lever customers; a Super Admin creates them. Each key is limited to the endpoints selected at creation; confidential postings and opportunities need a key created with confidential access.
- Test environment
- Lever provides sandbox environments to customers and partners on request.
- Rate limits
- Token bucket of 10 requests per second per key with bursts up to 20; HTTP 429 when exceeded.
- Pagination
- Opaque offset token from the next attribute while hasNext is true; limit 1-100.
- Provider events
- Webhooks for application created, stage change, archive state, hired and deletion events. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Offers are read-only and their fields (which include compensation) are not returned; only status and dates are mapped.
- Requisition compensation bands are not returned.
- Opportunity time filters use Lever's any-change semantics, which differ from the updatedAt attribute.
- File and resume uploads and downloads, panel and interview scheduling, feedback and form writes, user creation, posting applications (apply), uploads, webhooks and all deletes are not implemented. File and resume reads return metadata only, without download links.
- EEO responses and diversity surveys are never read. Application IP address, browser and custom question data are not returned. Feedback, form and referral answers omit currency fields and questions about salary, pay or other sensitive data.
- Requisition updates are not implemented: Lever's PUT replaces the whole requisition, so an update without the compensation band would erase it. Requisitions are created without a compensation band, and postings are created and updated without salary ranges.
- Archiving (opportunity_archive.update) keeps its existing optional cleanInterviews flag, which removes pending interviews; leave it unset to keep interviews.
- opportunities.list and users.list keep their existing optional email filters, which Lever only accepts as query parameters; avoid them where emails must not appear in request URLs.
- Opportunity, note, posting and requisition creates have no idempotency key; Lever de-duplicates contacts by email but still creates a new opportunity.
Developer reference
- Create the Employ Inc. credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Lever, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/lever and the Connections API.