// website builders and cms
Via APIWix email verification with pingutil
Wix member signups accept throwaway and mistyped addresses, and those members then sit in your contacts and receive your site emails. With Velo you can handle the wixMembers_onMemberCreated backend event, verify the login email with pingutil, and approve the member or block the login. With manual approval turned on, a new member is PENDING and cannot log in until your code approves them, which gets you close to blocking at sign-up.
Where it connects: Velo backend event wixMembers_onMemberCreated (events.js) with manual member approval
What goes wrong without it
- Our Wix members list is full of accounts nobody uses, and they all have weird random email addresses.
- We approve members by hand because of spam signups and it eats an hour every week.
- Site emails to new members bounce and Wix keeps flagging them as undeliverable contacts.
What you can do with Wix and pingutil
Auto-approve real members, hold the rest
Switch member signup to manual approval. The event handler verifies loginEmail and calls approveByEmail for valid, risky and unknown results, so real people get in without waiting.
Block disposable and dead mailboxes
When the status is invalid (disposable_domain, mailbox_not_found, no_mx), call blockByEmail. The member cannot log in, and approveByEmail undoes it if you change your mind.
Replace the manual review queue
Only results you choose to leave PENDING (for example risky accept_all addresses) stay in the queue for a human, instead of every new signup.
Set it up
- 1
In your member signup settings, set the approval policy to manual approval so new members start as PENDING.
- 2
Add your pingutil key to the Secrets Manager as PINGUTIL_API_KEY.
- 3
Turn on Dev Mode and create backend/events.js (or add to the existing one) with the handler below.
- 4
Publish the site; backend events do not run in Preview, so test with a real signup on the live site.
- 5
Sign up with a disposable address and with your own; check the members list to confirm one is blocked and one is approved.
import { fetch } from 'wix-fetch';
import { secrets } from 'wix-secrets-backend.v2';
import { elevate } from 'wix-auth';
import { authentication } from 'wix-members-backend';
const getSecretValue = elevate(secrets.getSecretValue);
function withTimeout(promise, ms) {
return Promise.race([promise, new Promise((_, reject) => setTimeout(() => reject(new Error('timeout')), ms))]);
}
async function verify(email) {
try {
const secret = await getSecretValue('PINGUTIL_API_KEY');
const key = typeof secret === 'string' ? secret : secret.value;
const res = await withTimeout(
fetch('https://pingutil.com/v1/verify', {
method: 'post',
headers: { Authorization: 'Bearer ' + key, 'Content-Type': 'application/json' },
body: JSON.stringify({ email }),
}),
20000,
);
if (!res.ok) return null; // 429 / 5xx: fail open
return await res.json();
} catch (err) {
console.error('pingutil check skipped', err);
return null; // timeout or network error: fail open
}
}
export async function wixMembers_onMemberCreated(event) {
const member = event.entity;
if (member.status !== 'PENDING' || !member.loginEmail) return;
const result = await verify(member.loginEmail);
if (result && result.status === 'invalid') {
console.log('blocking member', member._id, result.reason);
await authentication.blockByEmail(member.loginEmail);
return;
}
// valid, risky, unknown, or pingutil unreachable: let them in
await authentication.approveByEmail(member.loginEmail);
}What to do with each result
| pingutil result | Action in Wix |
|---|---|
| status: "invalid" | authentication.blockByEmail(loginEmail); the member cannot log in. |
| status: "valid" | authentication.approveByEmail(loginEmail). |
| status: "risky" (accept_all, role_based) | Approve, or skip the call to leave them PENDING for manual review. |
| status: "unknown" or no response | Approve; an outage should not lock out real members. |
Limits to plan for
- The member record already exists when the event fires. Manual approval is what keeps a flagged member from logging in; with automatic approval this becomes after-the-fact cleanup.
- Backend events do not run in Preview, and Wix forum threads report the event not firing for some signup setups, so confirm it on the live site before relying on it.
- Verification can take several seconds, so a valid member may wait a moment before their approval lands. The 300 verified addresses a day (3,000 a month) budget applies. Those are Free plan limits; Enterprise has custom limits.
Wix documentation
- dev.wix.com/docs/velo/events-service-plugins/members/events/on-member-created
- dev.wix.com/docs/velo/apis/wix-members-backend/authentication/approve-by-email
- dev.wix.com/docs/velo/apis/wix-members-backend/authentication/block-by-email
Wix is a trademark of its owner. This integration uses Wix's documented extension points; it is not an official Wix app.
Common questions
- Can I reject the signup before the Wix member is created?
- Not with the default signup form. The event runs after creation. Manual approval plus this handler means a flagged member never gets a working login, which covers most of the same ground.
- Does this work for Wix Forms submissions too?
- This handler only covers members. Form submissions are a different event; the same verify() helper can be reused there.
Stop bad addresses in Wix 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 Wix setup will receive.