Skip to content
Human resources ⇄ Database

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

Keep Lever and OpenSearch 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 OpenSearch

Put your workforce data where your apps can reach it: OpenSearch and Lever share the same people, positions, and org structure in real time.

Lever is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. OpenSearch is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Users, Stages, Feedback, Interviews in Lever need to exist as queryable Snapshots, Indexes, Documents, Index aliases in OpenSearch before an app can act on them. When that bridge is a nightly export or a hand-run CSV, every downstream system spends the day working from a roster that has already moved on.

Stacksync syncs Snapshots, Indexes, Documents, Index aliases in OpenSearch with Users, Stages, Feedback, Interviews in Lever field by field, in real time. You decide which system owns which fields — Lever typically owns identity and org attributes, while operational or computed values can flow back the other way — and Stacksync keeps every copy consistent, matching records on a stable key and resolving conflicts by rules you set.

The result is one live picture of the workforce on both sides: HR keeps its source of truth, and the database keeps a current mirror that internal apps, reports, and access controls can trust without a batch window in between.

Common use cases

  • 01 Sync product catalogs from an ERP or database into the indexes that back storefront search.
  • 02 Keep Postgres as the source of truth while mirroring rows to OpenSearch for full-text and vector queries.
  • 03 Consolidate Feedback, Interviews, and Notes into a warehouse for interviewer scorecard and time-to-fill reporting.
  • 04 Write enriched Sources, Tags, and Contact data back onto Opportunities from an outbound sourcing pipeline.

Common sync patterns

Computed and operational fields flow back

Values assembled or corrected in OpenSearch write onto the matching record in Lever where those fields are writable, keeping the people system enriched.

Mirror people records into the database

Records maintained in Lever land as queryable Snapshots, Indexes, Documents, Index aliases in OpenSearch, so internal apps and dashboards read live data instead of a periodic export.

One directory of record

When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.

What you can sync between Lever and OpenSearch

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 OpenSearch 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. Index templates Mapping and settings presets applied to new indexes a sync creates Interviews is specific to Lever and Index templates to OpenSearch — 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. Ingest pipelines Server-side processors that transform documents as they are written Notes and Contacts is specific to Lever and Ingest pipelines to OpenSearch — 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. Data streams Append-oriented time-series storage for logs and events pushed from source systems Opportunities is specific to Lever and Data streams to OpenSearch — 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. Snapshots Backup artifacts, relevant when reseeding an index from a repository Postings is specific to Lever and Snapshots to OpenSearch — 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. Indexes The core container; synced records land in indexes with defined mappings Requisitions is specific to Lever and Indexes to OpenSearch — 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. Documents JSON records written via the index and bulk APIs and read via search queries Offers is specific to Lever and Documents to OpenSearch — each maps to any object or custom field on the other side.

How changes propagate between Lever and OpenSearch

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

OpenSearch Lever Interval-based propagation

DetectionStacksync polls OpenSearch for changes on an incremental schedule, reading only records changed since the previous pass. No native 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.
  • OpenSearch: Throughput bounded by cluster sizing rather than fixed API quotas.
What ships with Lever ⇄ OpenSearch

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Lever ⇄ OpenSearch 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 OpenSearch.

How the Lever and OpenSearch 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

OpenSearch

Integration surface
REST API over HTTP(S) with JSON payloads
Authentication
basic authentication with the security plugin, or AWS IAM request signing on Amazon OpenSearch Service
Change detection
no native change feed; reads rely on queries with scroll or point-in-time polling
Capabilities
read · write
Rate limits
throughput bounded by cluster sizing rather than fixed API quotas
How it works

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

    Choose tables

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

Lever and OpenSearch 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 424 integrations available for Lever and OpenSearch.

Popular · 7 of 424
All Lever integrations All OpenSearch 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