# Dun & Bradstreet integrations: datasets

> Dun & Bradstreet is a business data provider that identifies companies by D-U-N-S Number and supplies firmographic, risk and partner data about them.

**Canonical page:** https://tray.ai/connectors/dun-and-bradstreet-integrations/
**Categories:** Sales
**Connects through:** HTTP Connector

## Overview

Dun & Bradstreet is a business data provider that identifies companies by D-U-N-S Number and supplies firmographic, risk and partner data about them. Tray.ai connects to Dun & Bradstreet through the HTTP Connector, so your workflows can call the Dun & Bradstreet API alongside the rest of your stack. API access comes through Dun & Bradstreet's partner program or API plan, so you need approved credentials first.

## Use cases

### Organizations

Read organizations in Dun & Bradstreet from any Tray.ai workflow. The Dun & Bradstreet API covers calls such as search organizations and get organization data by D-U-N-S.

- Search organizations
- Get organization data by D-U-N-S
- Count available organization records

### Datasets

Read and manage datasets in Dun & Bradstreet from any Tray.ai workflow. The Dun & Bradstreet API covers calls such as get dataset records for companies and batch get dataset records.

- Get dataset records for companies
- Batch get dataset records

## Challenges Tray.ai solves

### Keeping Dun & Bradstreet credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Dun & Bradstreet credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Dun & Bradstreet API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Dun & Bradstreet API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Dun & Bradstreet?

Yes. Tray.ai connects to Dun & Bradstreet through the HTTP Connector, which calls the Dun & Bradstreet API directly. Any call the Dun & Bradstreet API documents can run as a step in a Tray.ai workflow. API access comes through Dun & Bradstreet's partner program or API plan, so you need approved credentials first.

### How does Tray.ai authenticate with Dun & Bradstreet?

The Dun & Bradstreet API uses OAuth 2.0 and a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Dun & Bradstreet connector?

Dun & Bradstreet runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Dun & Bradstreet connector from the Dun & Bradstreet API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/