Skip to content
Human resources ⇄ Database

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

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

Put your workforce data where your apps can reach it: SingleStore 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. SingleStore is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Opportunities, Postings, Requisitions, Offers in Lever need to exist as queryable Indexes and Shard Keys, Databases, Tables (rowstore and columnstore), Views in SingleStore 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 Indexes and Shard Keys, Databases, Tables (rowstore and columnstore), Views in SingleStore with Opportunities, Postings, Requisitions, Offers 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 results of real-time analytical queries back into business tools where teams act on them.
  • 02 Consolidate data from transactional databases and SaaS apps into one store that handles both lookups and scans.
  • 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

Org and structure stay aligned

Groups, departments, managers, and reporting lines from Lever stay consistent in SingleStore, so hierarchy-driven logic and permissions don't drift.

Computed and operational fields flow back

Values assembled or corrected in SingleStore 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 Indexes and Shard Keys, Databases, Tables (rowstore and columnstore), Views in SingleStore, so internal apps and dashboards read live data instead of a periodic export.

What you can sync between Lever and SingleStore

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 SingleStore objects How this pairing syncs
Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. Reference Tables Small tables replicated to every node, often used for dimension data in syncs. Feedback is specific to Lever and Reference Tables to SingleStore — each maps to any object or custom field on the other side.
Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. Pipelines Native ingestion jobs from Kafka or object storage that coexist with external syncs. Interviews is specific to Lever and Pipelines to SingleStore — 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. Stored Procedures Existing logic sometimes invoked on write paths. Notes and Contacts is specific to Lever and Stored Procedures to SingleStore — 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. Indexes and Shard Keys Determine data distribution and lookup speed for sync match keys. Opportunities is specific to Lever and Indexes and Shard Keys to SingleStore — 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. Databases The connection target containing the tables a sync addresses. Postings is specific to Lever and Databases to SingleStore — 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. Tables (rowstore and columnstore) Primary read/write target; storage type affects whether a table suits point lookups or scans. Requisitions is specific to Lever and Tables (rowstore and columnstore) to SingleStore — each maps to any object or custom field on the other side.

How changes propagate between Lever and SingleStore

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 SingleStore 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 applied to SingleStore as a row-level write, with types converted between the two schemas.

SingleStore Lever Interval-based propagation

DetectionStacksync polls SingleStore for changes on an incremental schedule, reading only records changed since the previous pass. Polling on timestamp or watermark columns.

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.
  • SingleStore: No API rate limits; throughput is bounded by workspace or cluster size.
What ships with Lever ⇄ SingleStore

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

SingleStore

Integration surface
SQL over the MySQL wire protocol; an HTTP Data API is also available for SQL over REST
Authentication
Database credentials
Change detection
Polling on timestamp or watermark columns; the platform also provides change-observation features in recent versions
Capabilities
read · write
Rate limits
No API rate limits; throughput is bounded by workspace or cluster size
How it works

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

    Choose tables

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

Lever and SingleStore 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 449 integrations available for Lever and SingleStore.

Popular · 7 of 449
All Lever integrations All SingleStore 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