# Kickbox integrations

> Call the Kickbox API from any Tray.ai workflow with the HTTP Connector.

**Canonical page:** https://tray.ai/connectors/kickbox-integrations/
**Categories:** Data and analytics
**Connects through:** HTTP Connector

## Overview

Kickbox is an email verification service that checks whether addresses are deliverable, one at a time at sign-up or in bulk lists. Tray.ai connects to Kickbox through the HTTP Connector, so your workflows can call the Kickbox API alongside the rest of your stack.

## Use cases

### Single verification

Work with single verification in Kickbox from any Tray.ai workflow. The Kickbox API covers calls such as verify an email address and check a disposable domain.

- Verify an email address
- Check a disposable domain

### Batch verification

Create batch verification in Kickbox from any Tray.ai workflow. The Kickbox API covers calls such as start a batch verification and check batch job status.

- Start a batch verification
- Check batch job status

## Challenges Tray.ai solves

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

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

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

The Kickbox API uses an API key in the query string 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 Kickbox connector?

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