Skip to content
Database ⇄ Human resources

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

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

Put your workforce data where your apps can reach it: Jdbc 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. Jdbc 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 Stored procedures & functions, Sequences, Tables, Views in Jdbc 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 Stored procedures & functions, Sequences, Tables, Views in Jdbc 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 Connect a niche or legacy RDBMS that has no dedicated Stacksync connector but ships a JDBC driver, using its JDBC URL to sync it two-way.
  • 02 Incrementally sync a high-volume table by polling an updated_at or auto-increment column, keeping a downstream store fresh without full reloads.
  • 03 Push Postings and Requisitions into an HRIS or warehouse to reconcile approved headcount against open roles.
  • 04 When an Opportunity is marked hired, write the candidate and its Offer into an HRIS or onboarding system to start employee provisioning.

Common sync patterns

Computed and operational fields flow back

Values assembled or corrected in Jdbc 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 Stored procedures & functions, Sequences, Tables, Views in Jdbc, 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 Jdbc 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.

Jdbc objects Lever objects How this pairing syncs
Schemas & catalogs Namespaces that group tables and views; the connector targets a schema/catalog and lists its objects from the JDBC metadata to build the sync. 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. Schemas & catalogs is specific to Jdbc and Opportunities to Lever — each maps to any object or custom field on the other side.
Stored procedures & functions Server-side routines callable via JDBC CallableStatement; invoked for custom read or write logic when a table-level mapping is not enough. 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. Stored procedures & functions is specific to Jdbc and Postings to Lever — each maps to any object or custom field on the other side.
Sequences Server-generated identity values; relevant when writing rows into tables whose keys are assigned by the database rather than the source system. 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. Sequences is specific to Jdbc and Requisitions to Lever — each maps to any object or custom field on the other side.
Tables The base relational tables in the target database; synced two-way as rows over SQL, with each table's primary key driving upserts and row-level updates. 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. Tables is specific to Jdbc and Offers to Lever — each maps to any object or custom field on the other side.
Views Stored SELECT queries exposed like tables; read-only projections synced outbound when raw base tables should not be exposed downstream. Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. Views is specific to Jdbc and Users to Lever — each maps to any object or custom field on the other side.
Columns Per-table fields with data types, nullability, and defaults; enumerated via DatabaseMetaData.getColumns to auto-generate and type-check field mappings. Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. Columns is specific to Jdbc and Stages to Lever — each maps to any object or custom field on the other side.

How changes propagate between Jdbc 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.

Jdbc Lever Interval-based propagation

DetectionStacksync polls Jdbc 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.

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

Rate-limit considerations

  • Jdbc: No SaaS-style request quota. Throughput is bounded by the target database's max connections and connection-pool size, plus the CPU and I/O it shares with production queries, so heavy syncs can contend with live workloads.
  • 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 Jdbc ⇄ Lever

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Jdbc and Lever connectors work

Jdbc

Integration surface
JDBC API (java.sql / javax.sql) executing SQL through a JDBC driver, typically a pure-Java Type 4 driver; reaches any relational database with a driver - PostgreSQL, MySQL, SQL Server, Oracle, IBM DB2, and others - via a JDBC URL such as jdbc:postgresql://host:5432/db.
Authentication
A database user's username and password supplied in the JDBC connection (DriverManager or a DataSource), typically over a TLS/SSL-encrypted connection. Some drivers add Kerberos, integrated Windows auth, or cloud IAM-token auth, but the available methods depend on the target database and its driver.
Change detection
No native change feed. Incremental sync polls a cursor column - an updated_at timestamp or an auto-incrementing key - to pull new and changed rows; detecting deletes needs soft-delete flags or database triggers writing to a shadow table. No webhooks.
Capabilities
read · write
Rate limits
No SaaS-style request quota. Throughput is bounded by the target database's max connections and connection-pool size, plus the CPU and I/O it shares with production queries, so heavy syncs can contend with live workloads.

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 Jdbc 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 Jdbc 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
    Jdbc connected
    Lever connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Jdbc 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 431 integrations available for Jdbc and Lever.

Popular · 7 of 431
All Jdbc 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