# Reverse Contact integrations: enrichment

> Reverse Contact is a B2B data service that returns person and company profiles, finds work emails and phone numbers, and searches for people and…

**Canonical page:** https://tray.ai/connectors/reverse-contact-integrations/
**Categories:** Sales
**Connects through:** HTTP Connector

## Overview

Reverse Contact is a B2B data service that returns person and company profiles, finds work emails and phone numbers, and searches for people and companies matching criteria. Tray.ai connects to Reverse Contact through the HTTP Connector, so your workflows can call the Reverse Contact API alongside the rest of your stack.

## Use cases

### Enrichment

Update enrichment in Reverse Contact from any Tray.ai workflow. The Reverse Contact API covers calls such as enrich a person and enrich a company.

- Enrich a person
- Enrich a company

### People search

Read people search in Reverse Contact from any Tray.ai workflow. The Reverse Contact API covers calls such as search people and count people results.

- Search people
- Count people results
- Find lookalike people

### Company search

Read company search in Reverse Contact from any Tray.ai workflow. The Reverse Contact API covers calls such as search companies and count company results.

- Search companies
- Count company results

### Profiles

Read profiles in Reverse Contact from any Tray.ai workflow. The Reverse Contact API covers calls such as fetch a person profile and fetch a company profile.

- Fetch a person profile
- Fetch a company profile
- Check a live fetch status

### Contact details

Read contact details in Reverse Contact from any Tray.ai workflow. The Reverse Contact API covers calls such as find an email address and find a phone number.

- Find an email address
- Find a phone number

## Challenges Tray.ai solves

### Keeping Reverse Contact 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 Reverse Contact 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 Reverse Contact 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 Reverse Contact 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 Reverse Contact?

Yes. Tray.ai connects to Reverse Contact through the HTTP Connector, which calls the Reverse Contact API directly. Any call the Reverse Contact API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Reverse Contact?

The Reverse Contact API uses 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 Reverse Contact connector?

Reverse Contact runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Reverse Contact connector from the Reverse Contact 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/
