# Verifalia integrations: email verifications

> Submit a verification job and create a contact method in Verifalia, and start a workflow when Verifalia sends “Verification job completed”.

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

## Overview

Verifalia checks whether email addresses are valid and deliverable, one at a time or by cleaning whole mailing lists. Tray.ai connects to Verifalia through the HTTP Connector, so your workflows can call the Verifalia API alongside the rest of your stack.

## Use cases

### Email verifications

Read, create, and delete email verifications in Verifalia from any Tray.ai workflow. The Verifalia API covers calls such as submit a verification job and get job results.

- Submit a verification job
- Get job results
- List verification jobs

### Credits

Read credits in Verifalia from any Tray.ai workflow. The Verifalia API covers calls such as get the credits balance and get credit usage statistics.

- Get the credits balance
- Get credit usage statistics

### Users

Read, create, update, and delete users in Verifalia from any Tray.ai workflow. The Verifalia API covers calls such as list users and create a user.

- List users
- Create a user
- Update a user

### Contact methods

Read, create, and delete contact methods in Verifalia from any Tray.ai workflow. The Verifalia API covers calls such as list contact methods and create a contact method.

- List contact methods
- Create a contact method
- Delete a contact method

## Challenges Tray.ai solves

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

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

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

The Verifalia API uses basic authentication 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 Verifalia connector?

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