Skip to content
ERP ⇄ Human resources

DEAR Inventory to Lever integration — real-time, two-way sync

Keep DEAR Inventory and Lever 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 DEAR Inventory and Lever

Sync the workers, org structure, and cost centers that DEAR Inventory and Lever share in real time, so the people Lever manages stay current in the system that runs finance and operations.

Lever is the system of record for people: who was hired, which department and location they sit in, who they report to, and how they are paid. DEAR Inventory runs finance and operations, and much of what it does depends on that same information, from booking labor cost to approving an expense report to staffing a project. Where the two are bridged by re-keying or an overnight file, each side spends the day out of step, with new hires missing from the systems they need and leavers still active where they should not be.

Stacksync syncs Products, Stock levels, Sale orders, Purchase orders in DEAR Inventory with Interviews, Notes and Contacts, Opportunities, Postings in Lever field by field, in real time, and in both directions. You decide which system owns which fields, so the people side stays authoritative for worker data while DEAR Inventory keeps its own accounting and operational detail, and every change made in one is reflected in the other within seconds instead of at the next batch run.

Common use cases

  • 01 Keep supplier and purchase order data aligned with the accounting system for accrual accuracy.
  • 02 Sync stock levels and product data to e-commerce storefronts and a CRM so sales quotes reflect real availability.
  • 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

New hires ready to transact in DEAR Inventory

A new person set up in Lever becomes an employee record in DEAR Inventory in time to submit expenses, enter time, or approve a purchase, without waiting on manual setup.

One org structure

Departments, cost centers, and locations that both systems reference stay in agreement, so labor cost, approvals, and reporting in DEAR Inventory roll up to the same structure Lever maintains.

Reporting lines drive approvals

Manager and reporting-hierarchy changes in Lever keep expense and purchase approval chains in DEAR Inventory pointed at the right people.

What you can sync between DEAR Inventory and Lever

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.

DEAR Inventory objects Lever objects How this pairing syncs
Customers Buyer records aligned with CRM and accounting counterparts. 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. Customers is specific to DEAR Inventory and Requisitions to Lever — each maps to any object or custom field on the other side.
Suppliers Vendor records referenced on purchase orders. 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. Suppliers is specific to DEAR Inventory and Offers to Lever — each maps to any object or custom field on the other side.
Stock adjustments and transfers Inventory movement transactions that explain changes in availability. Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. Stock adjustments and transfers is specific to DEAR Inventory and Users to Lever — each maps to any object or custom field on the other side.
Assemblies / Production Bill-of-material and production records for light manufacturing workflows. Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. Assemblies / Production is specific to DEAR Inventory and Stages to Lever — each maps to any object or custom field on the other side.
Locations Warehouses and bins that scope stock levels and fulfillment. Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. Locations is specific to DEAR Inventory and Feedback to Lever — each maps to any object or custom field on the other side.
Products SKU records with pricing, suppliers, and bill-of-material links; the master data most syncs start from. Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. Products is specific to DEAR Inventory and Interviews to Lever — each maps to any object or custom field on the other side.

How changes propagate between DEAR Inventory and Lever

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.

DEAR Inventory Lever Sub-second propagation

DetectionDEAR Inventory notifies Stacksync of record changes through webhook events. Polling with modified-since filters.

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

Lever DEAR Inventory 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 DEAR Inventory through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • DEAR Inventory: Subject to the platform's per-account API rate limits.
  • 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.
What ships with DEAR Inventory ⇄ Lever

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever DEAR Inventory or Lever 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 DEAR Inventory or Lever record.

Observability

Monitoring

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

Trading partners

EDI

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

How the DEAR Inventory and Lever connectors work

DEAR Inventory

Integration surface
REST API
Authentication
Account ID plus application key sent as request headers
Change detection
Polling with modified-since filters; webhook notifications for sale and purchase events are available on subscriptions that include the Automation module
Capabilities
read · write · webhooks
Rate limits
Subject to the platform's per-account API rate limits

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
How it works

How to connect DEAR Inventory to Lever — 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 DEAR Inventory and Lever 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
    DEAR Inventory connected
    Lever connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the DEAR Inventory and Lever 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 · DEAR Inventory ⇄ Lever
    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
    DEAR Inventory Lever
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

DEAR Inventory and Lever 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 408 integrations available for DEAR Inventory and Lever.

Popular · 7 of 408
All DEAR Inventory integrations All Lever 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