Skip to content
Data warehouse ⇄ Human resources

Apache Kylin to Lever integration — real-time data sync

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

Land the people and organization records from Lever in Apache Kylin as live tables for workforce reporting, without extract jobs, and write computed results back where Lever can use them.

Apache Kylin is a read-only source: Stacksync reads its data in real time and delivers it into Lever, so Lever always reflects the current state of Apache Kylin — without exports, scripts, or schedulers.

Workforce data is some of the most requested data in the warehouse and some of the most awkward to move: the record types are many, the fields carry sensitive personal information, the APIs are strict, and hand-built extract jobs go stale or break quietly. Whether Lever is the system of record for employees and payroll, for candidates and applications, or for learners and course completions, the reporting belongs in Apache Kylin next to everything else the company measures.

Common use cases

  • 01 Trigger downstream syncs after segment build jobs complete so consumers only read refreshed data.
  • 02 Read pre-aggregated metrics from Kylin and sync them into CRM fields or planning spreadsheets on a schedule.
  • 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

Headcount and cost joined with everything else

Analysts combine Lever's workforce records with finance, product, or operational data already in Apache Kylin for reporting the HR system cannot produce on its own.

Fresh data instead of last night's load

Because changes stream continuously, reports query current workforce data rather than waiting for an overnight load window to finish.

Queryable history for planning and audit

A continuously synced copy in Apache Kylin gives you a durable, queryable record of how Lever's records change over time, for headcount planning and audit questions.

What you can sync between Apache Kylin 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 Kylin objects Lever objects How this pairing syncs
Projects Top-level workspaces that group models, tables, and jobs. 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. Projects is specific to Apache Kylin and Offers to Lever — each maps to any object or custom field on the other side.
Models Star-schema definitions over source tables that determine what can be queried. Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. Models is specific to Apache Kylin and Users to Lever — each maps to any object or custom field on the other side.
Cubes / Indexes Pre-computed aggregate structures that answer queries at low latency. Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. Cubes / Indexes is specific to Apache Kylin and Stages to Lever — each maps to any object or custom field on the other side.
Source Tables Hive or other upstream tables that builds read from. Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. Source Tables is specific to Apache Kylin and Feedback to Lever — each maps to any object or custom field on the other side.
Segments Time-ranged build units that partition pre-computed data. Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. Segments is specific to Apache Kylin and Interviews to Lever — each maps to any object or custom field on the other side.
Build Jobs Batch jobs that compute or refresh segments, monitored via the REST API. 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. Build Jobs is specific to Apache Kylin and Notes and Contacts to Lever — each maps to any object or custom field on the other side.

How changes propagate between Apache Kylin 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 Kylin Lever Interval-based propagation

DetectionStacksync polls Apache Kylin for changes on an incremental schedule, reading only records changed since the previous pass. Data freshness follows segment build and refresh jobs, so integrations poll query results.

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

Lever Apache Kylin Sub-second propagation

DetectionLever notifies Stacksync of record changes through webhook events. Webhooks for candidate and application lifecycle events (applicationCreated, candidateStageChange, candidateArchiveStateChange, candidateHired,.

DeliveryApache Kylin does not accept inbound record writes, so this direction carries requests rather than records: Apache Kylin's output flows back as field updates on the originating Lever records.

Rate-limit considerations

  • Apache Kylin: No fixed API quotas; query capacity depends on the deployment and pre-computed index coverage.
  • 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 Kylin ⇄ Lever

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

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

Real-time

Real-time sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Apache Kylin ⇄ 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 Kylin and Lever.

How the Apache Kylin and Lever connectors work

Apache Kylin

Integration surface
SQL over JDBC/ODBC plus a REST API for queries and administration
Authentication
Username/password (HTTP basic authentication on the REST API)
Change detection
Not applicable for row-level capture; data freshness follows segment build and refresh jobs, so integrations poll query results
Capabilities
read
Rate limits
No fixed API quotas; query capacity depends on the deployment and pre-computed index coverage

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

    Choose tables

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

Apache Kylin 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 392 integrations available for Apache Kylin and Lever.

Popular · 7 of 392
All Apache Kylin 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