# LeadBoxer integrations: lookups and leads

> Assign a lead, update a segment and add a dataset in LeadBoxer. Connect LeadBoxer to the rest of your sales stack with Tray.ai.

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

## Overview

LeadBoxer is a B2B lead identification tool that tracks website and email activity and matches visitors to companies and contacts for sales follow-up. Tray.ai connects to LeadBoxer through the HTTP Connector, so your workflows can call the LeadBoxer API alongside the rest of your stack.

## Use cases

### Lookups

Read lookups in LeadBoxer from any Tray.ai workflow. The LeadBoxer API covers calls such as look up an IP address and look up a domain.

- Look up an IP address
- Look up a domain
- Look up an email

### Leads

Read and update leads in LeadBoxer from any Tray.ai workflow. The LeadBoxer API covers calls such as retrieve leads and get lead details.

- Retrieve leads
- Get lead details
- Get lead sessions

### Segments

Read, update, and delete segments in LeadBoxer from any Tray.ai workflow. The LeadBoxer API covers calls such as retrieve segments and update a segment.

- Retrieve segments
- Update a segment
- Delete a segment

### Datasets

Create, update, and delete datasets in LeadBoxer from any Tray.ai workflow. The LeadBoxer API covers calls such as add a dataset and update a dataset name.

- Add a dataset
- Update a dataset name
- Remove a dataset

### Users

Create, update, and delete users in LeadBoxer from any Tray.ai workflow. The LeadBoxer API covers calls such as create a user and update a user name.

- Create a user
- Update a user name
- Delete a user

### Tracking

Manage tracking in LeadBoxer from any Tray.ai workflow. The LeadBoxer API covers calls such as track a server-side event and track an email open.

- Track a server-side event
- Track an email open

## Challenges Tray.ai solves

### Keeping LeadBoxer 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 LeadBoxer 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 LeadBoxer 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 LeadBoxer 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 LeadBoxer?

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

### How does Tray.ai authenticate with LeadBoxer?

The LeadBoxer API uses an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated LeadBoxer connector?

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