Skip to content
Human resources ⇄ Accounting and finance

Lever to Pigment integration — real-time, two-way sync

Keep Lever and Pigment in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Lever and Pigment

Keep the employee, department, and cost records that Pigment and Lever share consistent in real time, so the finance system and the people system stop drifting apart.

Pigment runs the money side of the company: who gets paid, what it costs, and which part of the business the cost belongs to. Lever runs the people side: who works here, which team they sit in, and how their employment changes over time. The two overlap on the same people and the same org structure, because every employee is also a payee and every department is also a cost center. When that overlap is maintained by hand, a new hire, a transfer, or a termination has to be keyed twice, and the two systems start to disagree about who is active and where the cost lands.

Stacksync syncs Users and permissions, Applications, Metrics, Dimension lists in Pigment with Postings, Requisitions, Offers, Users in Lever bi-directionally and in real time. A person added, updated, or deactivated on either side appears on the other within seconds, with field-level mapping and conflict resolution in place of CSV exports and nightly batch jobs.

That matters most when money follows a people event. A hire that finance can pay, a leaver whose access ends, a transfer that redirects cost to the right team, all happen from one change instead of two, so headcount and spend reconcile from the same set of records.

Common use cases

  • 01 Export approved budgets and forecasts back to a warehouse or Postgres for downstream reporting.
  • 02 Keep dimension lists such as departments and cost centers consistent with master data in the ERP.
  • 03 Two-way sync Opportunities and their Stages between Lever and a Postgres database so recruiting ops and analysts query the pipeline in SQL while recruiters keep working in Lever.
  • 04 Push Postings and Requisitions into an HRIS or warehouse to reconcile approved headcount against open roles.

Common sync patterns

One employee identity

A person's name, ID, or contact details corrected in either system update the other, so finance and HR reference the same person instead of maintaining two versions.

Department and cost-center alignment

The org structure maintained in Lever keeps the departments or cost centers in Pigment current, so spend and headcount roll up the same way.

Status changes propagate

A role, department, or employment-status change in either system updates the other within seconds, so cost allocation, access, and reporting reflect the current state.

What you can sync between Lever and Pigment

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Lever objects Pigment objects How this pairing syncs
Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. Dimension lists Master data like accounts, products, or employees that metrics are sliced by Interviews is specific to Lever and Dimension lists to Pigment — each maps to any object or custom field on the other side.
Notes and Contacts Free-text Notes on Opportunities plus the underlying Contact (person) that dedupes multiple Opportunities; notes are posted via POST /opportunities/:id/notes and contact-level tags, sources, and links can be added back for attribution. Tables Row-based transactional data loaded into models from source systems Notes and Contacts is specific to Lever and Tables to Pigment — each maps to any object or custom field on the other side.
Opportunities The core pipeline record for a candidate applying to a role; replaced the deprecated Candidates endpoint. Created via POST /opportunities and updated (stage, archive, links, tags, sources, files) through the API, and synced two-way with a database or HRIS. Scenarios Versions such as budget, forecast, and actuals that give exported figures their context Opportunities is specific to Lever and Scenarios to Pigment — each maps to any object or custom field on the other side.
Postings Job posting records with categories, apply URLs, workplace type, and requisition codes. Can be created via POST /postings and read into a warehouse for open-role reporting. Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model Postings is specific to Lever and Data imports to Pigment — each maps to any object or custom field on the other side.
Requisitions Headcount/requisition records with custom requisition fields, tied to Postings; read via GET /requisitions and synced to an HRIS to reconcile approved headcount against open roles. Users and permissions Access controls governing which model areas a sync can touch Requisitions is specific to Lever and Users and permissions to Pigment — each maps to any object or custom field on the other side.
Offers Offer records attached to an Opportunity with status and offer-form fields; exposed read-only through GET /opportunities/:id/offers, so they sync outbound to an HRIS or onboarding system when a candidate reaches the offer stage. Applications Planning models organized by domain such as finance, sales, or workforce Offers is specific to Lever and Applications to Pigment — each maps to any object or custom field on the other side.

How changes propagate between Lever and Pigment

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Lever Pigment Sub-second propagation

DetectionLever notifies Stacksync of record changes through webhook events. Webhooks for candidate and application lifecycle events (applicationCreated, candidateStageChange, candidateArchiveStateChange, candidateHired,.

DeliveryEach detected change is written to Pigment through its API, with automatic retries and rate-limit backoff.

Pigment Lever Interval-based propagation

DetectionStacksync polls Pigment for changes on an incremental schedule, reading only records changed since the previous pass. No change feed.

DeliveryEach detected change is written to Lever through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Lever: 10 requests/second per API key with a token-bucket burst to ~20/s; POSTs that create candidates/applications are throttled to roughly 2/second. Sustained overage returns 429 with Retry-After. List endpoints are cursor-paginated at up to 100 records per page.
  • Pigment: Subject to the platform's API rate limits.
What ships with Lever ⇄ Pigment

Connect Lever and Pigment for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Lever–Pigment connection.

Real-time

Two-way sync

Changes in Lever or Pigment instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Lever or Pigment data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Lever or Pigment record.

Observability

Monitoring

Track your Lever ⇄ Pigment sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Lever and Pigment.

How the Lever and Pigment connectors work

Lever

Integration surface
REST Data API (api.lever.co/v1)
Authentication
API key over HTTP Basic auth (key as username, blank password) for internal integrations, or OAuth 2.0 with 1-hour access tokens for partner integrations (auth.lever.co)
Change detection
Webhooks for candidate and application lifecycle events (applicationCreated, candidateStageChange, candidateArchiveStateChange, candidateHired, interview created/updated/deleted), plus incremental polling via created_at and updated_at range filters on Opportunities
Capabilities
read · write · webhooks
Rate limits
10 requests/second per API key with a token-bucket burst to ~20/s; POSTs that create candidates/applications are throttled to roughly 2/second. Sustained overage returns 429 with Retry-After. List endpoints are cursor-paginated at up to 100 records per page.
Lever setup guide

Pigment

Integration surface
REST-based import and export API
Authentication
API keys, issued separately for import and export
Change detection
no change feed; syncs run scheduled imports and exports
Capabilities
read · write
Rate limits
subject to the platform's API rate limits
How it works

How to connect Lever to Pigment — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Lever and Pigment with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Lever connected
    Pigment connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Lever and Pigment objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Lever ⇄ Pigment
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Lever Pigment
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Lever and Pigment integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 411 integrations available for Lever and Pigment.

Popular · 8 of 411
All Lever integrations All Pigment integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own