# Integrations

URL: https://email-validation.org/integrations/
Updated: 2026-10-20

> Documentation index: https://email-validation.org/llms.txt

Connect email validation to your stack with the REST API, the official SDKs, webhooks and the MCP server. Everything listed here exists today; we do not show logos for integrations we do not have.

## Build with the API

One request validates one address. Send your API key in the Authorization header.

```bash
curl https://api.email-validation.org/v1/validate \
  -H "Authorization: Bearer $EV_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email": "jane.doe@example.com"}'
```

```javascript
const res = await fetch('https://api.email-validation.org/v1/validate', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.EV_API_KEY}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({ email: 'jane.doe@example.com' }),
});
const result = await res.json();
console.log(result.status, result.reason, result.action);
```

```python
import os
import requests

res = requests.post(
    "https://api.email-validation.org/v1/validate",
    headers={"Authorization": f"Bearer {os.environ['EV_API_KEY']}"},
    json={"email": "jane.doe@example.com"},
    timeout=20,
)
result = res.json()
print(result["status"], result["reason"], result["action"])
```

- **[REST API](https://email-validation.org/docs/api-reference/)**: JSON over HTTPS, described by an OpenAPI 3.1 spec you can import into your tools. [API reference](https://email-validation.org/docs/api-reference/)
- **[JavaScript and TypeScript SDK](https://email-validation.org/docs/sdks/javascript/)**: Validate addresses, run bulk jobs and verify webhooks from Node.js, with typed results. [JavaScript SDK docs](https://email-validation.org/docs/sdks/javascript/)
- **[Python SDK](https://email-validation.org/docs/sdks/python/)**: The same operations from Python, with typed results. [Python SDK docs](https://email-validation.org/docs/sdks/python/)
- **[Webhooks](https://email-validation.org/docs/webhooks/)**: Signed calls to your URL when a bulk job finishes or your credits run low. [Webhook docs](https://email-validation.org/docs/webhooks/)
- **[MCP server](https://email-validation.org/integrations/mcp/)**: Let AI agents and MCP clients validate addresses with your API key. [MCP server](https://email-validation.org/integrations/mcp/)
- **[Code samples](https://email-validation.org/docs/code-samples/)**: Copy-paste examples in curl, JavaScript, TypeScript, Python, PHP, Ruby, Go, Java, C# and Rust. [Code samples](https://email-validation.org/docs/code-samples/)

## Works via HTTP

There are no native apps for these tools yet. Each of them can call our API through its HTTP request step, with your API key in the Authorization header. The [no-code recipes](https://email-validation.org/docs/guides/no-code/) show the exact setup.

- **Zapier**: Use a "Webhooks by Zapier" POST step to validate an address from any trigger. Works via HTTP
- **Make**: Use the HTTP "Make a request" module and map the result fields to the next step. Works via HTTP
- **n8n**: Use the HTTP Request node, with the API key stored as a header credential. Works via HTTP
- **Google Sheets**: Use Apps Script with UrlFetchApp to fill a status column for a sheet of addresses. Works via HTTP

## The same rules everywhere

- Every integration uses the same credits: one per definite result, unknown results free.
- Up to 500 requests per second per account after your first purchase (20 before).
- API keys go in the Authorization header, never in a URL and never in browser or mobile code.
- Test addresses on our sandbox domain are free, so you can wire up an integration without spending credits.