Skip to content
Database ⇄ Human resources

Apache Cassandra to Lever integration — real-time, two-way sync

Keep Apache Cassandra 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 Apache Cassandra and Lever

Put your workforce data where your apps can reach it: Apache Cassandra 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. Apache Cassandra is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Requisitions, Offers, Users, Stages in Lever need to exist as queryable Counters, Keyspaces, Tables, Partitions and Rows in Apache Cassandra 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 Counters, Keyspaces, Tables, Partitions and Rows in Apache Cassandra with Requisitions, Offers, Users, Stages 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 customer profile data between Cassandra and a CRM so operational apps and sales tools agree.
  • 02 Write attributes computed elsewhere (scores, preferences) back into Cassandra tables serving low-latency reads.
  • 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 Apache Cassandra, so hierarchy-driven logic and permissions don't drift.

Computed and operational fields flow back

Values assembled or corrected in Apache Cassandra 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 Counters, Keyspaces, Tables, Partitions and Rows in Apache Cassandra, so internal apps and dashboards read live data instead of a periodic export.

What you can sync between Apache Cassandra 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.

Apache Cassandra objects Lever objects How this pairing syncs
Collections List, set, and map columns handled with type-aware field mapping. 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. Collections is specific to Apache Cassandra and Notes and Contacts to Lever — each maps to any object or custom field on the other side.
Counters Increment-only counter columns, usually read-only in syncs. 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. Counters is specific to Apache Cassandra and Opportunities to Lever — each maps to any object or custom field on the other side.
Keyspaces Top-level namespaces with replication settings that scope a sync connection. 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. Keyspaces is specific to Apache Cassandra and Postings to Lever — each maps to any object or custom field on the other side.
Tables Wide-column tables addressed by partition key, the unit of row-level sync. 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 is specific to Apache Cassandra and Requisitions to Lever — each maps to any object or custom field on the other side.
Partitions and Rows Records located by partition and clustering keys during reads and upserts. 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. Partitions and Rows is specific to Apache Cassandra and Offers to Lever — each maps to any object or custom field on the other side.
Materialized Views Server-maintained denormalized views; considered experimental and disabled by default in recent releases. Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. Materialized Views is specific to Apache Cassandra and Users to Lever — each maps to any object or custom field on the other side.

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

Apache Cassandra Lever Sub-second propagation

DetectionChanges in Apache Cassandra are captured at the source via change data capture — no polling loop against its API. Commit-log based CDC on tables with CDC enabled, or polling using writetime metadata and timestamp columns.

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

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

Rate-limit considerations

  • Apache Cassandra: No API quotas; throughput is governed by cluster capacity and consistency-level choices.
  • 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 Apache Cassandra ⇄ Lever

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Apache Cassandra and Lever connectors work

Apache Cassandra

Integration surface
CQL over the Cassandra native binary protocol
Authentication
Database credentials (password authenticator); TLS and role-based grants where configured
Change detection
Commit-log based CDC on tables with CDC enabled, or polling using writetime metadata and timestamp columns
Capabilities
read · write · CDC
Rate limits
No API quotas; throughput is governed by cluster capacity and consistency-level choices

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

    Choose tables

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

Apache Cassandra 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 430 integrations available for Apache Cassandra and Lever.

Popular · 8 of 430
All Apache Cassandra 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