Skip to content
Human resources ⇄ Database

Lever to OCI Database (Oracle Cloud) integration — real-time, two-way sync

Keep Lever and OCI Database (Oracle Cloud) 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 OCI Database (Oracle Cloud)

Put your workforce data where your apps can reach it: OCI Database (Oracle Cloud) 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. OCI Database (Oracle Cloud) is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Notes and Contacts, Opportunities, Postings, Requisitions in Lever need to exist as queryable PL/SQL procedures and packages, JSON collections, Partitions, Tables in OCI Database (Oracle Cloud) 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 PL/SQL procedures and packages, JSON collections, Partitions, Tables in OCI Database (Oracle Cloud) with Notes and Contacts, Opportunities, Postings, Requisitions 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 Expose ERP or billing data held in OCI to internal tools by syncing selected schemas to a managed Postgres.
  • 02 Write changes from SaaS applications back into OCI so PL/SQL-based processes operate on current data.
  • 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

Reporting and analytics on current data

Notes and Contacts, Opportunities, Postings, Requisitions replicate into OCI Database (Oracle Cloud) where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.

Org and structure stay aligned

Groups, departments, managers, and reporting lines from Lever stay consistent in OCI Database (Oracle Cloud), so hierarchy-driven logic and permissions don't drift.

Computed and operational fields flow back

Values assembled or corrected in OCI Database (Oracle Cloud) write onto the matching record in Lever where those fields are writable, keeping the people system enriched.

What you can sync between Lever and OCI Database (Oracle Cloud)

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 OCI Database (Oracle Cloud) objects How this pairing syncs
Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. PL/SQL procedures and packages Server-side logic that can react to synced data or transform it in place Users is specific to Lever and PL/SQL procedures and packages to OCI Database (Oracle Cloud) — each maps to any object or custom field on the other side.
Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. JSON collections Document-style storage in the converged engine, synced alongside relational tables Stages is specific to Lever and JSON collections to OCI Database (Oracle Cloud) — each maps to any object or custom field on the other side.
Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. Partitions Physical table subdivisions relevant when replicating large fact tables Feedback is specific to Lever and Partitions to OCI Database (Oracle Cloud) — 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. Tables The primary sync surface; rows are read and written directly over SQL Interviews is specific to Lever and Tables to OCI Database (Oracle Cloud) — 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. Views Read-only projections used to expose curated subsets to downstream systems Notes and Contacts is specific to Lever and Views to OCI Database (Oracle Cloud) — 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. Materialized views Precomputed result sets sometimes used as stable read sources for replication Opportunities is specific to Lever and Materialized views to OCI Database (Oracle Cloud) — each maps to any object or custom field on the other side.

How changes propagate between Lever and OCI Database (Oracle Cloud)

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 OCI Database (Oracle Cloud) 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 OCI Database (Oracle Cloud) as a row-level write, with types converted between the two schemas.

OCI Database (Oracle Cloud) Lever Sub-second propagation

DetectionChanges in OCI Database (Oracle Cloud) are captured at the source via change data capture — no polling loop against its API. Log-based CDC from redo logs (LogMiner or GoldenGate), or timestamp polling.

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.
  • OCI Database (Oracle Cloud): Throughput bounded by instance sizing rather than API quotas.
What ships with Lever ⇄ OCI Database (Oracle Cloud)

Connect Lever and OCI Database (Oracle Cloud) for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Lever–OCI Database (Oracle Cloud) connection.

Real-time

Two-way sync

Changes in Lever or OCI Database (Oracle Cloud) instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Lever or OCI Database (Oracle Cloud) 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 OCI Database (Oracle Cloud) record.

Observability

Monitoring

Track your Lever ⇄ OCI Database (Oracle Cloud) 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 OCI Database (Oracle Cloud).

How the Lever and OCI Database (Oracle Cloud) 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

OCI Database (Oracle Cloud)

Integration surface
SQL wire protocol (Oracle Net) via JDBC, ODBC, and native drivers; ORDS REST optionally exposes tables over HTTP
Authentication
database credentials, commonly with mutual TLS using a client wallet on Autonomous Database; OCI IAM integration available
Change detection
log-based CDC from redo logs (LogMiner or GoldenGate), or timestamp polling
Capabilities
read · write · CDC
Rate limits
throughput bounded by instance sizing rather than API quotas
How it works

How to connect Lever to OCI Database (Oracle Cloud) — 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 OCI Database (Oracle Cloud) 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
    OCI Database (Oracle Cloud) connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Lever and OCI Database (Oracle Cloud) 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 434 integrations available for Lever and OCI Database (Oracle Cloud).

Popular · 8 of 434
All Lever integrations All OCI Database (Oracle Cloud) 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