Skip to content
Database ⇄ Human resources

IBM AS/400 to Lever integration — real-time, two-way sync

Keep IBM AS/400 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 IBM AS/400 and Lever

Put your workforce data where your apps can reach it: IBM AS/400 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. IBM AS/400 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 Members, Rows / records, Journals and journal receivers, Data queues in IBM AS/400 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 Members, Rows / records, Journals and journal receivers, Data queues in IBM AS/400 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 Keep customer and item files aligned with an ecommerce platform or modern ERP during phased modernization.
  • 02 Feed shipment and invoice data from the AS/400 into logistics and finance tools in near real time.
  • 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 IBM AS/400, so hierarchy-driven logic and permissions don't drift.

Computed and operational fields flow back

Values assembled or corrected in IBM AS/400 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 Members, Rows / records, Journals and journal receivers, Data queues in IBM AS/400, so internal apps and dashboards read live data instead of a periodic export.

What you can sync between IBM AS/400 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.

IBM AS/400 objects Lever objects How this pairing syncs
Rows / records The unit of read and write, accessed via SQL or record-level access. 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. Rows / records is specific to IBM AS/400 and Offers to Lever — each maps to any object or custom field on the other side.
Journals and journal receivers The change log that enables log-based CDC on journaled files. Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. Journals and journal receivers is specific to IBM AS/400 and Users to Lever — each maps to any object or custom field on the other side.
Data queues Program-to-program messaging objects sometimes used to hand events off to integrations. Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. Data queues is specific to IBM AS/400 and Stages to Lever — each maps to any object or custom field on the other side.
Libraries The schema-equivalent containers that scope which files a sync reads. Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. Libraries is specific to IBM AS/400 and Feedback to Lever — each maps to any object or custom field on the other side.
Physical files (tables) The Db2 for i tables mapped directly to sync targets. Interviews Scheduled interview panel events with times and interviewers; read for scheduling reporting and time-to-hire metrics, and creatable via the panels endpoint. Physical files (tables) is specific to IBM AS/400 and Interviews to Lever — each maps to any object or custom field on the other side.
Logical files (views) Indexed or filtered views over physical files, usable as read sources. 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. Logical files (views) is specific to IBM AS/400 and Notes and Contacts to Lever — each maps to any object or custom field on the other side.

How changes propagate between IBM AS/400 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.

IBM AS/400 Lever Sub-second propagation

DetectionChanges in IBM AS/400 are captured at the source via change data capture — no polling loop against its API. Journal-based CDC by reading journal receivers on journaled files.

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

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

Rate-limit considerations

  • IBM AS/400: Bounded by system resources and subsystem configuration rather than an API quota.
  • 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 IBM AS/400 ⇄ Lever

Connect IBM AS/400 and Lever for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every IBM AS/400–Lever connection.

Real-time

Two-way sync

Changes in IBM AS/400 or Lever instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever IBM AS/400 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 IBM AS/400 or Lever record.

Observability

Monitoring

Track your IBM AS/400 ⇄ Lever sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between IBM AS/400 and Lever.

How the IBM AS/400 and Lever connectors work

IBM AS/400

Integration surface
SQL over JDBC/ODBC to Db2 for i (for example the JTOpen/jt400 driver), alongside native record-level access
Authentication
IBM i user profile credentials (database credentials)
Change detection
Journal-based CDC by reading journal receivers on journaled files; polling as a fallback
Capabilities
read · write · CDC
Rate limits
Bounded by system resources and subsystem configuration rather than an API quota.

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

    Choose tables

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

IBM AS/400 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 433 integrations available for IBM AS/400 and Lever.

Popular · 7 of 433
All IBM AS/400 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