Real-time
Real-time sync
Changes in Dun And Bradstreet or Lever instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Human resources
Dun And Bradstreet to Lever integration — real-time data sync
Keep Dun And Bradstreet 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 Dun And Bradstreet and Lever
Flow Dun And Bradstreet data into Lever in real time — no exports, no schedulers, no custom scripts.
Dun And Bradstreet 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 Dun And Bradstreet — without exports, scripts, or schedulers.
Dun And Bradstreet runs on people as much as on accounts: every contact, deal, and account has an owner, and those owners are employees whose roles, teams, and status are held in Lever. Lever is the system of record for the workforce, from new hires to promotions to departures, and often for the candidates the business is still deciding on. When the two systems are connected only by re-keying or an overnight export, they drift apart, and the CRM ends up assigning accounts to people who have left, holding territories that no longer match the org chart, and waiting days to give a new rep access.
Common use cases
- 01 Build target-account lists with Criteria Search and land the resulting DUNS plus firmographics in a database for outbound and TAM analysis.
- 02 Poll D&B Monitoring notifications for a registered portfolio of key accounts and suppliers and update the CRM or warehouse record whenever a firmographic or risk score changes.
- 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
One directory of people
A person's name, title, email, phone, or manager corrected in either system updates the other, so both stop maintaining separate copies of the same individual.
Where Lever tracks people the business also engages: contacts stay in sync
A person recorded in Lever, such as a candidate or applicant, can create or update the matching contact in Dun And Bradstreet, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.
New team members provisioned when they are hired
When Lever records a new hire, a matching user or owner is created in Dun And Bradstreet, so a new rep can start working accounts without waiting on a manual setup ticket.
What you can sync between Dun And Bradstreet 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.
| Dun And Bradstreet objects | Lever objects | How this pairing syncs | |
|---|---|---|---|
| Monitoring Notifications Change notices for a registered portfolio of DUNS; read-only feed pulled from the notifications endpoint (retained ~60 days) or delivered as bundled push. | 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. | Monitoring Notifications is specific to Dun And Bradstreet and Postings to Lever — each maps to any object or custom field on the other side. | |
| Company Information (Data Block) Core firmographics for a D-U-N-S Number - legal name, addresses, industry codes, employees, sales, status. Retrieved read-only via the Enrich endpoint; blocks come in levels L1-L4. | 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. | Company Information (Data Block) is specific to Dun And Bradstreet and Requisitions to Lever — each maps to any object or custom field on the other side. | |
| Principals & Contacts (Data Block) Company officers, executives, and contacts tied to a D-U-N-S Number; read-only enrichment used to populate CRM contact and account-owner fields. | 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. | Principals & Contacts (Data Block) is specific to Dun And Bradstreet and Offers to Lever — each maps to any object or custom field on the other side. | |
| Company Hierarchy & Connections (Family Tree) Parent, subsidiary, branch, and global-ultimate DUNS relationships; read-only, used to build account hierarchies and corporate-family rollups. | Users Lever team members (recruiters, hiring managers) with configurable roles; can be created via POST /users, deactivated, and reactivated through the API. | Company Hierarchy & Connections (Family Tree) is specific to Dun And Bradstreet and Users to Lever — each maps to any object or custom field on the other side. | |
| Financial Strength & Risk Insight (Data Block) D&B risk and credit signals - D&B Rating, PAYDEX, Failure Score, Delinquency Score, Viability - keyed by D-U-N-S Number; read-only. | Stages Pipeline stage definitions that Opportunities move through; read to model funnel state and stage transitions in a database. | Financial Strength & Risk Insight (Data Block) is specific to Dun And Bradstreet and Stages to Lever — each maps to any object or custom field on the other side. | |
| Identity Resolution (Match / cleanseMatch) Sends a company name and address and returns ranked candidate DUNS with confidence codes and a MatchGrade; read-only scored match, not an exact lookup. | Feedback Interview feedback and scorecard forms attached to Opportunities; created via POST /opportunities/:id/feedback and consolidated into a warehouse for interviewer analytics. | Identity Resolution (Match / cleanseMatch) is specific to Dun And Bradstreet and Feedback to Lever — each maps to any object or custom field on the other side. |
How changes propagate between Dun And Bradstreet 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.
Dun And Bradstreet Lever Interval-based propagation
DetectionStacksync polls Dun And Bradstreet for changes on an incremental schedule, reading only records changed since the previous pass. Polling via D&B Monitoring - register a portfolio of DUNS and pull change notices from the notifications endpoint (retained ~60 days).
DeliveryEach detected change is written to Lever through its API, with automatic retries and rate-limit backoff.
Lever Dun And Bradstreet Sub-second propagation
DetectionLever notifies Stacksync of record changes through webhook events. Webhooks for candidate and application lifecycle events (applicationCreated, candidateStageChange, candidateArchiveStateChange, candidateHired,.
DeliveryDun And Bradstreet does not accept inbound record writes, so this direction carries requests rather than records: Dun And Bradstreet's output flows back as field updates on the originating Lever records.
Rate-limit considerations
- Dun And Bradstreet: Per-contract transactions-per-second cap plus weekly/monthly/yearly quotas; exceeding TPS returns HTTP 429 with error 0045/0046 (0047 on spike arrest). Quotas reset on UTC boundaries.
- 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 Dun And Bradstreet ⇄ Lever
Connect Dun And Bradstreet and Lever for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dun And Bradstreet–Lever connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Dun And Bradstreet 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 Dun And Bradstreet or Lever record.
Observability
Monitoring
Track your Dun And Bradstreet ⇄ Lever sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Dun And Bradstreet and Lever.
How the Dun And Bradstreet and Lever connectors work
Dun And Bradstreet
- Integration surface
- D&B Direct+ REST API (plus.dnb.com) - capability groups for Identity Resolution (Match), Search, Enrich (Data Blocks by D-U-N-S Number), Multi-Process, Data File/Batch, and Monitoring
- Authentication
- OAuth 2.0 client-credentials: Base-auth a consumer key/secret to POST /v3/token for a bearer token; access tokens expire after 24 hours.
- Change detection
- Polling via D&B Monitoring - register a portfolio of DUNS and pull change notices from the notifications endpoint (retained ~60 days). Bundled push delivery is configured with your D&B rep; there is no standard HTTP webhook and no log-based CDC.
- Capabilities
- read
- Rate limits
- Per-contract transactions-per-second cap plus weekly/monthly/yearly quotas; exceeding TPS returns HTTP 429 with error 0045/0046 (0047 on spike arrest). Quotas reset on UTC boundaries.
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.
How it works
How to connect Dun And Bradstreet 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.
- 01
Connect your apps
Authenticate Dun And Bradstreet 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.
Dun And Bradstreet
connected
Lever
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Dun And Bradstreet 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.
objects · Dun And Bradstreet ⇄ LeverCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Dun And Bradstreet LeverCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Dun And Bradstreet and Lever integration FAQ
-
Yes. Stacksync provides a managed, real-time integration between Dun And Bradstreet and Lever — Dun And Bradstreet is a read-only source, so data flows from it into the other system: authenticate both systems, choose the objects to sync, map fields visually, and changes propagate in milliseconds — no code required.
-
Dun And Bradstreet is a read-only source, so this integration runs one-way: Stacksync reads from Dun And Bradstreet in real time and delivers into Lever. Field mapping and monitoring work the same as for two-way pairs.
-
Common patterns for Dun And Bradstreet and Lever: One directory of people; Where Lever tracks people the business also engages: contacts stay in sync; New team members provisioned when they are hired. A person's name, title, email, phone, or manager corrected in either system updates the other, so both stop maintaining separate copies of the same individual.
-
Dun And Bradstreet: D&B Direct+ REST API (plus.dnb.com) - capability groups for Identity Resolution (Match), Search, Enrich (Data Blocks by D-U-N-S Number), Multi-Process, Data File/Batch, and Monitoring. Authentication: OAuth 2.0 client-credentials: Base-auth a consumer key/secret to POST /v3/token for a bearer token; access tokens expire after 24 hours. Lever: 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). Stacksync manages authentication, retries, and rate limits on both sides.
-
Dun And Bradstreet: D&B Direct+ is a reference-data / enrichment API - read and enrich only. You retrieve firmographics, contacts, hierarchy, and risk scores for a D-U-N-S Number; there is no endpoint to write business records back into D&B. Lever: List endpoints use cursor-based pagination at up to 100 records per page; incremental syncs rely on created_at and updated_at range filters. Stacksync's field mapping accounts for these differences between Dun And Bradstreet and Lever without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Dun And Bradstreet and Lever records are not retained after a sync operation.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 483 integrations available for Dun And Bradstreet and Lever.
Popular · 7 of 483
-
Dun And Bradstreet ⇄ Namely -
Dun And Bradstreet ⇄ Paylocity -
Dun And Bradstreet ⇄ Ukg Ready -
Lever ⇄ Attio -
Lever ⇄ Pipedrive -
Lever ⇄ Zoho CRM -
Lever ⇄ Shopify
No integrations match .
