.png)
Dun & Bradstreet Integration Guide
Connect Dun & Bradstreet Direct+ REST APIs with enterprise workflows to match, enrich, screen, and synchronize business data.
Dun & Bradstreet integration options at a glance
Dun & Bradstreet Direct+ primarily provides REST APIs secured with an OAuth 2.0-style client-credential flow. Enterprise workflows can use these APIs to search and match businesses, retrieve company profiles, obtain D-U-N-S Numbers, access corporate linkage, and consume licensed risk, compliance, financial, supplier, or ESG data. General-purpose webhooks, outbound callbacks, GraphQL, SOAP, bulk APIs, and direct database access were not confirmed for the core Direct+ product. Martini can securely acquire bearer tokens, call the relevant endpoints, validate and transform responses, apply match and entitlement rules, and write approved data to applications, databases, or internal APIs.
| Integration point | Supported by Dun & Bradstreet? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | D&B Direct+ REST endpoints support business search, company matching, company profiles, D-U-N-S Number retrieval, corporate linkage, and licensed enrichment or risk products. | Martini workflows consume the endpoints, construct authenticated requests, validate responses, apply business rules, and route results to downstream systems. |
| Authentication | Yes | D&B Direct+ uses an OAuth 2.0-style client-credential flow with D&B-issued client credentials and bearer access tokens. | Martini can store credentials in protected environment configuration, acquire and reuse valid tokens, and keep environments isolated. |
| Webhooks / outbound callbacks | Not confirmed | No general-purpose D&B Direct+ webhook or outbound callback model was confirmed. | Martini should use synchronous API calls or scheduled workflows rather than assume vendor-initiated events. |
| GraphQL APIs | Not confirmed | No official D&B GraphQL API documentation was confirmed for Direct+. | Martini can use the documented REST interface instead of representing the integration as GraphQL-based. |
| SOAP APIs | Not confirmed | No current SOAP interface was confirmed for D&B Direct+; separately licensed legacy services should not be assumed. | Martini can consume SOAP where a separately confirmed D&B service exists, but it is not the recommended Direct+ model. |
| Bulk / async / batch APIs | Not confirmed | D&B has separate data-delivery offerings, but a generally available Direct+ bulk or asynchronous API was not confirmed. | Martini can implement controlled scheduled retrieval when supported by the subscribed endpoint, without assuming batch semantics. |
| File / attachment APIs | Not confirmed | No general file or attachment API was confirmed for the core Direct+ REST product. | Martini should use REST responses unless a specific D&B file-delivery arrangement is separately documented. |
| Database access | No | Direct customer database or analytics access is not the documented D&B integration model. | Martini consumes D&B APIs and can write approved results to customer-controlled databases through supported database capabilities. |
| Scheduled synchronization | Limited | Recurring refreshes can query D&B for controlled D-U-N-S Numbers or other permitted identifiers when webhook coverage is unavailable. | Martini scheduler-triggered workflows can poll at governed intervals, compare values, and update downstream systems with bounded retries. |
How Dun & Bradstreet exposes data and business events
Dun & Bradstreet REST APIs
D&B Direct+ is primarily a synchronous REST API product for searching and matching businesses, retrieving profiles and D-U-N-S Numbers, obtaining corporate linkage, and accessing licensed data products such as risk, compliance, financial, supplier, or ESG information.
Martini implementation pattern
Martini implementation pattern: a workflow receives a request from an application or API, obtains a valid D&B bearer token, calls the product-specific endpoint, validates the response, applies match and entitlement rules, and maps approved data to the target system.
Implementation sequence
Dun & Bradstreet Authentication
Protected D&B Direct+ endpoints use D&B-issued client credentials to obtain an access token, followed by bearer-token authorization on API requests. Products and scopes depend on the tenant’s subscription and entitlements.
Martini implementation pattern
Martini implementation pattern: credentials remain in protected environment configuration, a workflow obtains or reuses a token, and request handling detects expiration or authentication failures without exposing secrets in mappings or logs.
Implementation sequence
Scheduled D&B Refresh
General-purpose D&B webhooks or outbound callbacks were not confirmed, so recurring synchronization is better implemented by querying controlled identifiers on a schedule. Refresh scope must respect API quotas, subscriptions, and data-use terms.
Martini implementation pattern
Martini implementation pattern: a scheduler starts a workflow, the workflow retrieves due D-U-N-S Numbers or permitted identifiers, calls the applicable D&B endpoint, compares current and stored values, and writes only approved changes with retry controls.
Implementation sequence
Common Dun & Bradstreet integration patterns
Pattern 1: Enrich CRM companies with D-U-N-S Numbers
When to use this pattern
Use this pattern when a CRM creates or changes an Account and sales, master-data, or reporting processes need a verified D&B identity and selected company attributes. Ambiguous or low-confidence matches should not be automatically accepted.
Integration direction
Example Mapping
| Dun & Bradstreet Field | Canonical Field | Target Field |
|---|---|---|
| organization.primaryName | company.name | Account.Name |
| organization.primaryAddress.addressCountry | company.country | Account.BillingCountry |
| dunsNumber | company.dunsNumber | Account.DUNS_Number__c |
| organization.primaryIndustryCode | company.industryCode | Account.Industry_Code__c |
Martini implementation pattern
A Martini workflow receives the CRM change, normalizes identity fields, calls the D&B matching endpoint, evaluates confidence and address consistency, and maps the selected D-U-N-S Number and approved attributes back to Salesforce. It routes multiple or ambiguous matches for review and uses the D-U-N-S Number and source identifier to prevent duplicate updates.
Martini capabilities used
- workflows
- API consumption
- OAuth 2.0 authentication
- data mapping
- business rules
- error handling
Pattern 2: Screen suppliers during onboarding
When to use this pattern
Use this pattern when procurement or supplier-management processes need D&B identity, ownership, compliance, or risk information before approving a supplier. The exact results depend on the subscribed D&B product and permissions.
Integration direction
Example Mapping
| Dun & Bradstreet Field | Canonical Field | Target Field |
|---|---|---|
| supplier.legalName | supplier.name | ServiceNow supplier.name |
| supplier.address.country | supplier.country | ServiceNow supplier.country |
| dunsNumber | supplier.dunsNumber | ServiceNow supplier.dunsNumber |
| complianceScreeningResult.status | supplier.screeningStatus | ServiceNow supplier.screeningStatus |
Martini implementation pattern
Martini receives the onboarding request, validates required supplier fields, calls entitled D&B identity and screening APIs, and applies internal approval thresholds. Approved results return to ServiceNow; missing data, entitlement failures, no matches, and ambiguous matches become distinct exception outcomes rather than blind retries.
Martini capabilities used
- API-led workflows
- validation
- data mapping
- business rules
- conditional routing
- error handling
Pattern 3: Refresh customer and supplier master data
When to use this pattern
Use this pattern when downstream systems require periodic updates to company profiles, classifications, corporate linkage, or licensed risk attributes and D&B does not provide a confirmed general-purpose webhook model.
Integration direction
Example Mapping
| Dun & Bradstreet Field | Canonical Field | Target Field |
|---|---|---|
| dunsNumber | organization.dunsNumber | BusinessPartner.externalDunsNumber |
| organization.registeredName | organization.legalName | BusinessPartner.legalName |
| organization.corporateLinkage.parentDunsNumber | organization.parentDunsNumber | BusinessPartner.parentId |
| organization.industryCode | organization.industryCode | BusinessPartner.industryCode |
Martini implementation pattern
A scheduled Martini workflow selects controlled identifiers, retrieves current D&B data, compares it with stored snapshots, and sends only changed approved attributes to SAP. It records retrieval timestamps and source metadata, applies rate-limit backoff, and resumes safely using checkpoints or idempotent keys.
Martini capabilities used
- scheduler triggers
- workflows
- API consumption
- data mapping
- change detection
- retry handling
Pattern 4: Synchronize corporate hierarchies to analytics
When to use this pattern
Use this pattern when account rollups, supplier-family analysis, or ownership-aware reporting requires D&B parent, subsidiary, headquarters, branch, and related-company relationships.
Integration direction
Example Mapping
| Dun & Bradstreet Field | Canonical Field | Target Field |
|---|---|---|
| dunsNumber | organization.dunsNumber | company.duns_number |
| corporateLinkage.parentDunsNumber | organization.parentDunsNumber | company.parent_duns_number |
| corporateLinkage.relationshipType | organization.relationshipType | company_relationship.relationship_type |
| organization.primaryName | organization.name | company.company_name |
Martini implementation pattern
Martini retrieves the subscribed corporate-linkage response, validates nested relationship structures, separates company and relationship writes, and loads versioned data into Snowflake. Invalid structures, entitlement gaps, and transient API failures are logged separately so a refresh can be retried without duplicating hierarchy rows.
Martini capabilities used
- scheduled workflows
- API consumption
- JSON handling
- data mapping
- database integration
- error handling
Applications commonly integrated with Dun & Bradstreet
Dun & Bradstreet data can be incorporated into enterprise master-data, onboarding, risk, analytics, and account-management processes. The following are practical integration targets; availability depends on each application’s APIs and the organization’s D&B subscription and data entitlements.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Salesforce | Enrich Accounts, improve company matching, store D-U-N-S Numbers, and support account hierarchy management. | Salesforce → Martini → Dun & Bradstreet | A Martini workflow receives a new or changed Account, normalizes identity fields, calls the applicable D&B matching API, applies confidence rules, and returns approved firmographic or hierarchy data to Salesforce. |
| Microsoft Dynamics 365 | Validate and enrich account or supplier information during CRM and onboarding processes. | Microsoft Dynamics 365 → Martini → Dun & Bradstreet | Martini consumes Dynamics 365 changes or API requests, calls D&B Direct+ with normalized company attributes, maps the response, and routes ambiguous matches for review before updating Dynamics 365. |
| SAP S/4HANA | Improve customer and supplier master data, legal-entity identification, and corporate-family reporting. | SAP S/4HANA → Martini → Dun & Bradstreet | A workflow reads approved SAP master-data changes, retrieves D&B company and linkage information, preserves the D-U-N-S Number as a cross-system key, and writes governed attributes back to SAP or an MDM process. |
| ServiceNow | Support vendor onboarding, third-party risk, and company identity validation in procurement or risk workflows. | ServiceNow → Martini → Dun & Bradstreet | Martini receives a ServiceNow onboarding request, calls the relevant D&B search and screening APIs, applies internal approval rules, and returns an enriched supplier profile or exception status. |
| Workday | Validate organizations and suppliers used in procurement and related business processes. | Workday → Martini → Dun & Bradstreet | Martini orchestrates the Workday-to-D&B lookup, maps organization identifiers and approved attributes, and sends validated results to Workday while recording provenance and review outcomes. |
| Oracle NetSuite | Improve customer and vendor records and attach D-U-N-S Numbers to finance and procurement master data. | Oracle NetSuite → Martini → Dun & Bradstreet | A workflow retrieves NetSuite customer or vendor data, performs D&B matching, prevents duplicate updates using source identifiers and D-U-N-S Numbers, and writes approved enrichment to NetSuite. |
| Coupa | Support supplier onboarding, supplier identity matching, and risk or compliance review. | Coupa → Martini → Dun & Bradstreet | Martini receives supplier details from Coupa, queries entitled D&B identity and risk services, evaluates business rules, and returns an onboarding decision or routes an exception for manual review. |
| Snowflake | Centralize D&B company, hierarchy, risk, or enrichment data for analytics and master-data processes. | Dun & Bradstreet → Martini → Snowflake | A scheduled Martini workflow retrieves permitted D&B data for controlled identifiers, validates and normalizes the payload, and loads versioned results into Snowflake with retrieval timestamps and source metadata. |
How to build a Dun & Bradstreet integration in Martini
Objective
Configure the D&B API environment and target-system credentials without embedding secrets in workflows or mappings.
Instructions in Martini
- Create separate development, test, and production configurations.
- Store D&B client credentials in protected Martini environment configuration.
- Confirm D&B product subscriptions, scopes, headers, quotas, and target-system access.
Objective
Select an event, API request, or schedule that matches the integration use case and D&B’s synchronous API model.
Instructions in Martini
- Use an application request for on-demand matching or enrichment.
- Use a scheduler for recurring refreshes because general D&B webhooks were not confirmed.
- Define controlled selection criteria for D-U-N-S Numbers and source records.
Objective
Acquire a valid bearer token and call the product-specific D&B endpoint with normalized matching or retrieval inputs.
Instructions in Martini
- Normalize company name, address, country, registration, and other available identifiers.
- Acquire or reuse a valid OAuth 2.0-style access token.
- Call the subscribed REST endpoint and handle pagination only according to that endpoint’s documented behavior.
Objective
Coordinate authentication, API calls, validation, matching, target writes, and exception routing in a maintainable Martini workflow.
Instructions in Martini
- Separate lookup and matching from downstream persistence where practical.
- Branch for no match, multiple matches, entitlement errors, and technical failures.
- Preserve correlation identifiers, source values, and retrieval metadata for auditability.
Objective
Convert the D&B product response into a canonical company, hierarchy, screening, or assessment model before writing it downstream.
Instructions in Martini
- Map only fields available under the subscribed D&B product.
- Treat optional and masked values as nullable.
- Preserve the D-U-N-S Number and source provenance when a match is accepted.
Objective
Ensure that matching, screening, data governance, and duplicate-prevention policies are enforced before downstream updates.
Instructions in Martini
- Require acceptable match confidence before assigning a D-U-N-S Number.
- Route ambiguous or conflicting matches to manual review.
- Apply retention, access, redistribution, and decision-use policies to sensitive data.
Common Dun & Bradstreet data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Business / Organization | Company identity, legal name, location, registration information, industry classification, and firmographic enrichment. | Salesforce, Microsoft Dynamics 365, SAP S/4HANA, Snowflake | Martini validates the product-specific response, normalizes fields, applies entitlement and match rules, and maps approved attributes to the target model. |
| D-U-N-S Number | Stable Dun & Bradstreet identifier for a business location or organization and a cross-system matching key. | Salesforce, SAP S/4HANA, Oracle NetSuite, master-data platforms | Martini stores the D-U-N-S Number after acceptable match confidence, uses it for idempotency and refreshes, and preserves the original matching evidence. |
| Corporate Linkage | Parent, subsidiary, branch, headquarters, and related-company relationships. | SAP S/4HANA, Salesforce, Snowflake, data warehouses | Martini maps relationship types and identifiers into hierarchy models, validates optional nested structures, and records retrieval provenance. |
| Beneficial Owner | Ownership and control information for entitled due-diligence and know-your-business processes. | ServiceNow, Coupa, compliance platforms, Snowflake | Martini applies access and retention rules, treats fields as product-dependent, and routes sensitive results only to authorized targets. |
| Compliance Screening Result | Business screening and risk-related results where the subscribed D&B product permits access. | ServiceNow, Coupa, procurement applications, case-management systems | Martini validates status and response metadata, applies approval rules, distinguishes exceptions from technical errors, and records audit information. |
| ESG Assessment | Environmental, social, and governance indicators or assessment data where the organization has the relevant D&B entitlement. | Snowflake, SAP S/4HANA, supplier-management platforms | Martini maps the subscribed product schema, preserves assessment dates and provenance, and handles absent or masked attributes defensively. |
Authentication and security considerations
OAuth 2.0-style authentication
Dun & Bradstreet Direct+ uses D&B-issued client credentials to obtain access tokens, followed by bearer-token authorization on protected REST requests.
- Store client identifiers, secrets, tokens, and endpoint configuration in protected Martini environment configuration.
- Keep development, test, and production credentials separate.
- Reuse valid tokens where appropriate and reauthenticate when tokens expire.
- Confirm product entitlements, scopes, headers, and data-access permissions for each credential.
- Use HTTPS and avoid exposing credentials or sensitive screening, ownership, and ESG data in logs.
Operational considerations for Dun & Bradstreet integrations
Quotas and data usage
Confirm D&B rate limits, quotas, subscription entitlements, and retention or redistribution restrictions. Use controlled schedules, bounded backoff, and permitted caching rather than aggressive polling.
Matching and identity
Company-name-only searches can be ambiguous. Combine address, country, postal code, registration, telephone, and other available inputs, and distinguish legal entities from headquarters, branches, and parents.
Reliability and data quality
- Use D-U-N-S Numbers, source identifiers, or composite keys for idempotency.
- Handle endpoint-specific pagination and optional or masked fields defensively.
- Separate no-match and ambiguous-match outcomes from technical failures.
- Retry transient service and rate-limit failures with bounded backoff, but do not blindly retry invalid requests.
- Review mappings when D&B products, versions, countries, or entitlements change.
- Test against representative product responses and monitor workflow logs and correlation identifiers.
Why use Martini instead of scripts or point-to-point integrations?
Orchestration instead of isolated scripts
Martini provides a maintainable workflow layer around D&B REST calls, authentication, matching decisions, transformations, target writes, and exception routing. This avoids duplicating token handling and business rules across point-to-point scripts.
Reusable integration assets
Teams can expose internal APIs for on-demand enrichment, reuse mappings and validation logic, and combine D&B data with CRM, procurement, ERP, database, or analytics processes.
Operational control
- Centralize environment-specific secrets and API configuration.
- Implement schedules, conditional routing, retries, and idempotent writes consistently.
- Preserve provenance, correlation information, and review outcomes.
- Adapt mappings to product-specific D&B schemas without coupling every target directly to the vendor response.
Frequently asked questions
Dun & Bradstreet Direct+ can be integrated primarily through REST APIs secured with an OAuth 2.0-style client-credential flow. Enterprise workflows can search and match businesses, retrieve D-U-N-S Numbers and company profiles, obtain corporate linkage, and access licensed risk, compliance, financial, supplier, or ESG data. Because general-purpose webhooks were not confirmed, recurring synchronization is typically implemented with scheduled API requests.
Yes. Martini can consume Dun & Bradstreet Direct+ REST APIs, securely obtain bearer tokens, normalize request data, validate and transform responses, apply matching and entitlement rules, and write approved results to applications, databases, or internal APIs.
No dedicated Dun & Bradstreet connector is required. Martini can integrate using D&B’s confirmed native REST APIs and OAuth 2.0-style authentication, with workflows handling requests, mappings, business rules, retries, and downstream updates.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Dun & Bradstreet. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Dun & Bradstreet, cloud infrastructure, or other third-party systems based on subscription, usage, and deployment model.
The recommended method for new Direct+ integrations is the D&B REST API with OAuth 2.0-style client authentication. GraphQL, current SOAP, general-purpose webhooks, outbound callbacks, a generally available bulk API, and direct database access were not confirmed for the core Direct+ product.
No general-purpose D&B Direct+ webhook or outbound callback capability was confirmed. On-demand enrichment can still be near real time when another application invokes a Martini API or workflow, while recurring refreshes should use controlled scheduled workflows.
A Martini workflow can receive source-system changes or run on a schedule, call D&B for matching or refresh data, compare the response with stored values, and update approved downstream fields. D-U-N-S Numbers, source identifiers, and composite business keys can support idempotency and duplicate prevention.
Martini maps product-specific D&B responses into canonical and target models, validates optional nested structures, and applies business rules before writing data. Workflows can distinguish authentication, entitlement, rate-limit, transient service, no-match, ambiguous-match, and persistence errors, using bounded retries for transient failures and manual review for uncertain matches.
Related Martini documentation
Workflows
Integrate Dun & Bradstreet with Martini
Use Martini to connect Dun & Bradstreet Direct+ data with enterprise workflows, applications, and governed data processes.