Three primitives.
Glue them yourself.
KillBounce does not ship a directory of branded ESP connectors. It ships a clean API, webhooks, and CSV — and shows you the wiring patterns that get those into any stack today.
Three primitives.
That's it.
No fake catalog of one-click ESP connectors. Three surfaces, all production-ready, that compose into anything your stack needs.
REST API
OpenAPI spec, bearer auth, idempotent calls. The same surface the dashboard runs on — anything the UI does, an API key can do.
Webhooks
Async bulk-job results POST to your endpoint on completion, with retry-with-backoff if your receiver is briefly down.
CSV upload
Drag-and-drop in the dashboard. We dedupe before billing, auto-detect the email column, and stream results back as a downloadable CSV.
We do not have a one-click
Mailchimp connector.
Every other verifier's integrations page lists 20 logos — most of which resolve to a Zapier recipe behind the scenes. We do not pre-build those because they break the moment a vendor changes their API. The patterns below are what actually scale.
- N°01PLATE 10·B·A
Pre-send list scrub
Before your ESP fires a campaign, push the segment through a Zapier / Make / n8n recipe that calls our bulk endpoint, waits for the webhook, then filters back to your ESP with only the addresses that returned Valid.
§ Works with Mailchimp, Klaviyo, HubSpot, Brevo, ActiveCampaign, anything with a Zap / Make integration.
- N°02PLATE 10·B·B
Signup-form gating
On every new signup, your backend calls /verify/single with the submitted address. If the result is Invalid or Risky, return a soft "did you mean…" prompt before persisting the contact.
§ Works in any backend — Node, Python, PHP, Ruby, Go. Curl + 20 lines.
- N°03PLATE 10·B·C
Quarterly re-engagement scrub
Export the inactive segment from your ESP, push it through a bulk verification job (the dashboard or the API are equivalent), and re-import only the addresses that came back Valid. Saves a chunk on profile-based pricing.
§ CSV in, CSV out. Works for everyone.
Tell us
what you need.
The API is open. If you need a maintained ESP connector and are willing to pay for the engineering time to build and maintain it, email sales@getkillbounce.com with the specifics. Otherwise the no-code patterns above are the path.
§ Live · versioned · idempotent