Reduce manual data entry
Auto-sync candidates and postings to remove duplicate work.
Lever Connector
Embed Lever-powered recruiting automations that sync candidate, posting, interview and offer data across customer accounts. Build reusable workflows to create and update candidates, post jobs, trigger hiring notifications and keep ATS data synchronized inside your product.
Faster time to hire
Trigger notifications and downstream tasks automatically on hire.
Multi-tenant orchestration
Run isolated workflows per customer account with shared templates.
Embedded experience
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
Overview
Integrate Lever to automate candidate lifecycle, job posting and hiring notifications between your product and customers’ Lever accounts. Use Cyclr to map postings, create or update candidates and opportunities, subscribe to Lever webhooks, and orchestrate cross-system workflows that reduce manual entry and speed hiring outcomes.
PRODUCT USE CASES
Top Use Cases for Lever Integrations
Keep your customers in your SaaS by embedding Lever automations. Connect candidate and posting events, provision downstream HR tools, and surface hiring notifications directly inside your app for a smoother hiring experience.
Sync new candidates to CRM or ATS-linked tools
On applicationCreated or candidateCreated webhook, push candidate fields to CRM records and create follow-up tasks.
Publish job postings from your product
Create or update Lever postings via API so customers manage jobs centrally from your app.
Notify hiring teams on candidate stage changes
Subscribe to candidateStageChange or candidateHired webhooks and trigger in-app alerts or Slack messages.
ORCHESTRATION
How Lever works with Cyclr
Cyclr sits between your SaaS product and Lever to handle authentication, govern access and orchestrate every API call per customer, at scale.
- 1
Your SaaS product
Your app requests an action for a specific customer.
- 2
Cyclr orchestration
Cyclr authenticates, applies policies and routes the request.
- 3
Lever
Lever processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Available connector capabilities
Explore Lever methods you can orchestrate through Cyclr.
Users1
List Users
ActionOpportunities11
List New Opportunities
ActionLists all pipeline opportunities created since the last run date.
Update Opportunity Stage
ActionChange an opportunities current stage.
Remove Tags From Opportunity
ActionRemove tags from an opportunity.
Update Opportunity Archived State
ActionChange an opportunities archived state.
Add Opportunity Sources
ActionAdd sources to an opportunity.
List Opportunities
ActionLists all pipeline opportunities in your Lever account.
Get Opportunity
ActionGets a single pipeline opportunity in your Lever account.
List Updated Opportunities
ActionLists all pipeline opportunities updated since the last run date.
Remove Opportunity Sources
ActionRemove sources from an opportunity.
Create Opportunity
ActionCreates an opportunity in your Lever account.
Add Tags To Opportunity
ActionAdds tags to a opportunity.
Candidates1
Add Candidate Postings
ActionAdd postings to a candidate.
Contacts2
Get Contact
ActionGet the specified contact.
Update Contact
ActionUpdate the specified contact.
TECHNICAL DETAILS
Lever integration and API details
Review the sourced authentication and API behaviour used when configuring customer-facing Lever integrations in Cyclr.
API and authentication
- API host
https://api.lever.co/v1- Authentication
- API key; OAuth 2.0
- Credentials
API key (Basic auth username); OAuth client_id, client_secret and exact redirect_uri.
- Method categories
CRUD endpoints for candidates, postings, opportunities, interviews, offers, users, files and webhooks.
Pagination and rate limits
Pagination
Offset-based pagination: limit 1–100, responses include an opaque next offset token for subsequent pages.
Rate limits
Default 10 requests/second per API key with bursts up to 20/sec; use exponential backoff on 429.
IMPLEMENTATION
Authentication at a glance
Lever supports API keys (Basic auth with key as username) and OAuth 2.0 Authorization Code. Confirm which authentication options Cyclr exposes in your Console.
- Authentication method
- API key; OAuth 2.0
- Credential required
API key (Basic auth username); OAuth client_id, client_secret and exact redirect_uri.
Before you begin:
View setup guideWebhooks require Super Admin; OAuth requires app registration and exact redirect URI.
COMMON QUESTIONS
Frequently asked questions
It automates candidate, posting, opportunity, interview and offer workflows between your app and customers’ Lever accounts. Use API create/read/update endpoints and Lever webhooks to sync records, post jobs and trigger hiring notifications.
Lever supports API keys (Basic auth with the key as the username) and OAuth 2.0 Authorization Code. Cyclr may expose one or both methods — verify which options are enabled in your Cyclr Console.
Yes. Cyclr supports multi-tenant embedded delivery so you can store per-customer credentials and run isolated workflows for each account while reusing templates.
Yes. You can expose create/read/update actions and webhook-driven automations as governed MCP tools in Cyclr’s marketplace; confirm the exact methods in Console.
KEEP EXPLORING
Related resources and connectors
Documentation
What is iPaaS?
Read more →ProductHow to develop an API – Best Practices to Follow from Cyclr Developers
Read more →ProductMCP PaaS
Read more →Related connectorInstant.co
Related Miscellaneous connector for customer-facing integration workflows.
Related connectorLeap API
Related Miscellaneous connector for customer-facing integration workflows.
Related connectorLiveForce
Related Miscellaneous connector for customer-facing integration workflows.