// email marketing and newsletters
Via APIIterable email verification with pingutil
Iterable journeys enroll every new user, so fake and mistyped addresses get the same welcome and promotional email as real customers, and their bounces count against your sender reputation. A Call Webhook tile sends each new user to your endpoint, pingutil verifies the address, and the Iterable API writes the result to a data field that journey filters and segments can use.
Where it connects: Iterable journey Call Webhook tile plus the API POST /api/users/update endpoint
What goes wrong without it
- Bounces from brand-new users keep showing up in our deliverability reports, and they all come from the first welcome email.
- Promo signups bring in throwaway addresses, and they inflate our audience counts for every campaign.
- We want a single profile field that every team can filter on before they send.
What you can do with Iterable and pingutil
Verify on journey entry
Place the Call Webhook tile right after the journey start, then a short delay and a Yes/No split on the emailVerification data field.
Exclude risky users from bulk campaigns
Build a dynamic list on emailVerification.status so blast campaigns skip invalid, risky and unknown profiles while triggered email still goes to risky ones.
Catch typo signups
Write did_you_mean to the profile and trigger an in-app or push message asking the user to correct their address.
Set it up
- 1
Create a server-side Iterable API key and a pingutil API key.
- 2
Deploy the endpoint below and protect it with a shared secret header.
- 3
In your journey, add a Call Webhook tile after the start tile, set it to POST your endpoint URL with the secret header and a JSON body containing {{email}}.
- 4
Add a delay of at least a minute (Iterable suggests a buffer after user updates), then a Yes/No split on emailVerification.status.
- 5
Test with a user profile that has a known-bad address and confirm the data field is written.
# Call Webhook tile body: {"email": "{{email}}"} Header: X-Webhook-Secret: <secret>
import os
import threading
import requests
from flask import Flask, abort, request
app = Flask(__name__)
ITERABLE = {"Api-Key": os.environ["ITERABLE_API_KEY"]}
def verify(email):
try:
r = requests.post(
"https://pingutil.com/v1/verify",
headers={"Authorization": "Bearer " + os.environ["PINGUTIL_KEY"]},
json={"email": email},
timeout=30,
)
return r.json() if r.ok else None # quota or server error: fail open
except requests.RequestException:
return None
def handle(email):
v = verify(email)
if v is None:
return
requests.post(
"https://api.iterable.com/api/users/update",
headers=ITERABLE,
json={
"email": email,
"dataFields": {
"emailVerification": {
"status": v["status"],
"reason": v["reason"],
"didYouMean": v["did_you_mean"],
"checkedAt": v["checked_at"],
}
},
"mergeNestedObjects": True,
},
timeout=15,
)
@app.post("/hooks/iterable")
def iterable_hook():
if request.headers.get("X-Webhook-Secret") != os.environ["HOOK_SECRET"]:
abort(401)
email = (request.get_json(force=True) or {}).get("email", "")
if "@" in email:
# Iterable allows 10 seconds per webhook call; verify in the background.
threading.Thread(target=handle, args=(email,), daemon=True).start()
return "", 200What to do with each result
| pingutil result | Action in Iterable |
|---|---|
| status: "invalid" | Write emailVerification.status and route the user out of the journey; exclude the value from every list. |
| status: "risky", reason: "accept_all" | Allow triggered email, exclude from bulk promotional lists. |
| status: "unknown" | Keep sending triggered email and re-verify before adding to large campaigns. |
| didYouMean is set | Send an in-app message asking the user to confirm or fix the address. |
Limits to plan for
- Iterable gives journey webhooks a fixed 10-second timeout and retries up to 3 times after 3-minute delays, so answer immediately and verify afterwards as the snippet does.
- Iterable recommends leaving at least 60 seconds between a user update and steps that depend on it; put a delay tile before the split.
- pingutil checks up to 300 addresses per account per day (3,000 a month); higher signup volumes need Enterprise limits or a fast /v1/lookup screen. Those are Free plan limits.
Iterable documentation
Iterable is a trademark of its owner. This integration uses Iterable's documented extension points; it is not an official Iterable app.
Common questions
- Can I unsubscribe invalid users instead of just tagging them?
- Yes. Iterable has subscription management endpoints you can call from the same handler, but many teams prefer a data field because it is easy to undo and works for every channel decision.
- Why store the result as a nested object?
- Keeping status, reason and the check date together makes it easy to re-verify users whose last check is old without adding several top-level fields.
Stop bad addresses in Iterable today
Sign in with your email, create an API key and paste it into the step above. Test on a few real addresses first: the live demo shows exactly what your Iterable setup will receive.