Skip to content
Database ⇄ Human resources

Azure Cosmos DB to Lever integration — real-time, two-way sync

Keep Azure Cosmos DB 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 Azure Cosmos DB and Lever

Put your workforce data where your apps can reach it: Azure Cosmos DB 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. Azure Cosmos DB is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Offers, Users, Stages, Feedback in Lever need to exist as queryable Partition keys, Change feed entries, Stored procedures and triggers, Databases in Azure Cosmos DB 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 Partition keys, Change feed entries, Stored procedures and triggers, Databases in Azure Cosmos DB with Offers, Users, Stages, Feedback 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 Mirror Cosmos DB items into Postgres so teams can query operational data with standard SQL.
  • 02 Two-way sync between a Cosmos DB-backed product catalog and a PIM or commerce platform.
  • 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 Azure Cosmos DB 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 Partition keys, Change feed entries, Stored procedures and triggers, Databases in Azure Cosmos DB, 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 Azure Cosmos DB 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.

Azure Cosmos DB objects Lever objects How this pairing syncs
Stored procedures and triggers Server-side logic scoped to a partition; relevant when writes must respect existing validation. 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. Stored procedures and triggers is specific to Azure Cosmos DB and Requisitions to Lever — each maps to any object or custom field on the other side.
Databases Top-level namespaces that scope containers and throughput provisioning. 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. Databases is specific to Azure Cosmos DB and Offers to Lever — each maps to any object or custom field on the other side.
Containers The unit of partitioning and throughput; each container maps to a synced collection. Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. Containers is specific to Azure Cosmos DB and Users to Lever — each maps to any object or custom field on the other side.
Items (JSON documents) Schema-flexible JSON records read and written during sync; nested structures are flattened or mapped as needed. Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. Items (JSON documents) is specific to Azure Cosmos DB and Stages to Lever — each maps to any object or custom field on the other side.
Partition keys Determine data distribution and must be included on writes for the sync to route items correctly. Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. Partition keys is specific to Azure Cosmos DB and Feedback to Lever — each maps to any object or custom field on the other side.
Change feed entries Ordered record of inserts and updates per partition, consumed for incremental sync. Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. Change feed entries is specific to Azure Cosmos DB and Interviews to Lever — each maps to any object or custom field on the other side.

How changes propagate between Azure Cosmos DB 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.

Azure Cosmos DB Lever Sub-second propagation

DetectionChanges in Azure Cosmos DB are captured at the source via change data capture — no polling loop against its API. Built-in change feed exposing inserts and updates in order within each partition key range.

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

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

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.
What ships with Azure Cosmos DB ⇄ Lever

Connect Azure Cosmos DB and Lever for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Azure Cosmos DB and Lever.

How the Azure Cosmos DB and Lever connectors work

Azure Cosmos DB

Integration surface
REST API and SDKs over HTTPS (API for NoSQL, formerly the SQL API); also MongoDB, Cassandra, Gremlin, and Table API surfaces
Authentication
Account keys, resource tokens, or Microsoft Entra ID role-based access
Change detection
Built-in change feed exposing inserts and updates in order within each partition key range
Capabilities
read · write · CDC

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

    Choose tables

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

Azure Cosmos DB 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 438 integrations available for Azure Cosmos DB and Lever.

Popular · 7 of 438
All Azure Cosmos DB 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