An email verification API where verification is not a second step
Most lead workflows have two vendors: one that finds contacts and one that tells you whether the addresses still work. TAPAC collapses both into a single call — POST /v1/contacts/search returns the person and the SMTP result for that mailbox together. If you only need the check, POST /v1/contacts/verify takes a list of addresses and answers for each one.
Why the split costs you more than money
- 40% of emails go dead within two years (NeverBounce) — a list verified last quarter is not verified now.
- 23% of contacts change jobs every year (ZoomInfo, 2025), so the address you verified for a person may now belong to their replacement's predecessor.
- Static databases typically bounce 10–35%; TAPAC returns 2–5% because the handshake happens at request time rather than at import time.
Bounces are not a data-quality metric, they are a deliverability liability: every hard bounce counts against the sending domain you are trying to warm up.
Endpoints
| Call | What you get back |
|---|---|
POST /v1/contacts/search | Contacts (name, title, company, source) with each email already SMTP-verified. |
POST /v1/contacts/verify | Per-address verification results for a list you already have. |
GET /v1/contacts/{{id}} | One contact you fetched earlier, including its verification status. |
GET /v1/status | API version, key state and remaining quota. |
Call it
curl -X POST https://tapacapi.com/v1/contacts/verify \
-H "Authorization: Bearer $TAPAC_API_KEY" \
-H "Content-Type: application/json" \
-d '{"emails":["alex@example.com","sam@example.com"]}'
Or from the SDK:
npm install @tapacapi/sdk
import { TapacClient } from "@tapacapi/sdk";
const tapac = new TapacClient({ apiKey: process.env.TAPAC_API_KEY });
await tapac.verifyEmails(["alex@example.com", "sam@example.com"]);
Machine-readable spec: /openapi.json (OpenAPI 3.1). Sandbox: add the header X-Sandbox: true to any call and you get sample data with no production side effects.
How it is priced
100 free searches, then $0.10–0.50 per verified contact, pay-per-use — no seat licence and no annual contract. That is the whole model: you pay for contacts that exist rather than for a plan that expects you to send to whatever the database still has on file.
Where it is the wrong tool
If you need free-text enrichment of millions of stored rows, or a full CRM with a browser extension, TAPAC is not that. It is an API and an MCP server for finding people and knowing, at the moment of use, whether the mailbox is real.
Where to go next
- REST API quickstart — endpoints, Bearer auth, sandbox header, OpenAPI 3.1 spec at
/openapi.json. - Get a free API key — 100 searches, no credit card.
- Verify email before sending · Lead generation MCP server · Install the MCP server
- Compare TAPAC with Apollo, ZoomInfo, Hunter and Lusha · Apollo alternative · ZoomInfo alternative · Hunter alternative · Lusha alternative