// auth and identity
Via APIPing Identity email verification with pingutil
A PingOne DaVinci registration flow creates whatever account the form collects, so throwaway and scripted addresses become directory users. Put an HTTP connector node with the Make REST API Call capability between the registration form and the node that creates the user: it sends the address to pingutil, and a Functions connector comparison routes disposable or randomized addresses back to the form with an error.
Where it connects: PingOne DaVinci registration flow, HTTP connector "Make REST API Call" capability with a Functions connector branch
What goes wrong without it
- Our DaVinci registration flow is clean on the canvas, but the PingOne directory still fills with users at temp-mail domains.
- We do not want to write and host custom code just to say no to a throwaway address.
- Every bad sign-up we let in still gets a verification email, and those bounce.
What you can do with Ping Identity and pingutil
Reject disposable addresses inside the registration flow
The Make REST API Call node calls POST /v1/lookup with skip_enrichment: true. When rawResponse.body.verdict.is_spam is true, an A == B node sends the user to an error message instead of the create-user step.
Catch machine-generated addresses on any domain
Bots register strings like xk29qz8w@ at domains no list knows. verdict.reason randomized_local_part trips the same branch, so the flow stops them without a domain list of your own.
Send work-email sign-ups down a different path
Compare rawResponse.body.category with "company" in a second Functions node. Work addresses can go to a sales-assisted onboarding branch while free webmail sign-ups take the self-serve path.
Set it up
- 1
Create a pingutil API key in the pingutil dashboard and store it in DaVinci > Variables as a secret value, as Ping recommends for credentials.
- 2
In the DaVinci flow that handles registration, add an HTTP connector node after the form that collects the email, select the Make REST API Call capability, set the URL to https://pingutil.com/v1/lookup and the HTTP Method to POST.
- 3
Add an authorization header with the value Bearer followed by your key variable, and a raw JSON body with input set to the email variable from the form node and skip_enrichment set to true.
- 4
Set Timeout (ms) to about 2000 and paste the schema below into the Success Response Schema field, so later nodes can pick verdict and category fields.
- 5
Add a Functions connector A == B node that compares verdict.is_spam with true; route true to an HTTP Custom HTML Message (or back to the form) and false to the node that creates the user.
- 6
Route the HTTP node's failure outcome to the create-user node too, so a pingutil timeout or 429 does not block real people, then test with a disposable address.
{
"type": "object",
"properties": {
"domain": { "type": "string" },
"category": {
"type": "string",
"enum": ["company", "free", "disposable", "educational", "government", "isp", "unknown"]
},
"verdict": {
"type": "object",
"properties": {
"is_spam": { "type": "boolean" },
"low_trust": { "type": "boolean" },
"reason": { "type": ["string", "null"] }
}
},
"email_signals": {
"type": ["object", "null"],
"properties": {
"is_randomized": { "type": "boolean" },
"is_role_based": { "type": "boolean" }
}
}
}
}What to do with each result
| pingutil result | Action in Ping Identity |
|---|---|
| verdict.is_spam: true, reason "disposable_domain" | A == B true branch: show an error and ask for a permanent address |
| verdict.is_spam: true, reason "randomized_local_part" | Same true branch; do not create the user |
| verdict.low_trust: true (role, system or sales address) | Continue to create the user; optionally set a user attribute for review |
| category: "company" | Optional branch to a work-email onboarding path |
| Timeout, 429 or 5xx (node failure) | Failure outcome connects to the create-user node (fail open) |
Limits to plan for
- Ping documents a maximum of 29,000 ms for the Make REST API Call timeout when the field is blank. A full mailbox check with /v1/verify fits, but users wait while it runs; fast-mode /v1/lookup keeps the registration step quick.
- The check only covers registrations that pass through this DaVinci flow. Users created by administrators, imports or other PingOne APIs skip it. PingFederate and other Ping products use their own extension points, not covered here.
- Each registration counts toward 2,000 lookups a day (30,000 a month) per account, or 300 verified addresses a day (3,000 a month) with /v1/verify. Those are Free plan limits; Enterprise has custom limits.
Ping Identity documentation
- docs.pingidentity.com/connectors/http_connector.html
- docs.pingidentity.com/connectors/functions_connector.html
Ping Identity is a trademark of its owner. This integration uses Ping Identity's documented extension points; it is not an official Ping Identity app.
Common questions
- Can I block bad emails in PingOne without writing code?
- Yes, in a DaVinci flow. The HTTP connector calls pingutil and a Functions connector compares the result, so the whole check is nodes on the canvas. You still need a pingutil API key stored as a DaVinci variable.
- Should the DaVinci node call /v1/verify or /v1/lookup?
- Use /v1/lookup with skip_enrichment set to true to block disposable and randomized addresses in milliseconds. Use /v1/verify when you also want to stop dead mailboxes and typos and can accept a few seconds of wait on first-seen addresses.
Stop bad addresses in Ping Identity 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 Ping Identity setup will receive.