From dc3bcc2109bc13e11dccbe35b0a2b0536a726b9a Mon Sep 17 00:00:00 2001 From: Gregory Oschwald Date: Fri, 9 Oct 2026 20:59:24 +0000 Subject: [PATCH] Document email verification inputs Add /email/verification_time and /email/was_verification_successful to the minFraud request docs and the request examples. Add a release note for the new inputs. Co-Authored-By: Claude Opus 5.5 --- .../minfraud/api-documentation/requests.md | 20 +++++++++++++++++-- ...026-10-26-new-email-verification-inputs.md | 13 ++++++++++++ 2 files changed, 31 insertions(+), 2 deletions(-) create mode 100644 content/minfraud/release-notes/2026-10-26-new-email-verification-inputs.md diff --git a/content/minfraud/api-documentation/requests.md b/content/minfraud/api-documentation/requests.md index 86c753739..0687d4ad4 100644 --- a/content/minfraud/api-documentation/requests.md +++ b/content/minfraud/api-documentation/requests.md @@ -121,7 +121,9 @@ size will be rejected. }, "email": { "address": "977577b140bfb7c516e4746204fbdb01", - "domain": "maxmind.com" + "domain": "maxmind.com", + "verification_time": "2026-10-01T14:25:00Z", + "was_verification_successful": true }, "event": { "party": "customer", @@ -353,7 +355,9 @@ the end-user who initiated the event. ```json { "address": "977577b140bfb7c516e4746204fbdb01", - "domain": "maxmind.com" + "domain": "maxmind.com", + "verification_time": "2026-10-01T14:25:00Z", + "was_verification_successful": true } ``` @@ -371,6 +375,18 @@ the end-user who initiated the event. You do not need to pass the email domain input unless you are passing the email address as an MD5 hash. [Learn more about hashed email inputs on our Knowledge Base.](https://support.maxmind.com/knowledge-base/articles/passing-email-inputs-minfraud#email-hashing) {{}} + + {{< minfraud-schema-row key="verification_time" type="request" valueType="string" >}} + The most recent date and time a verification of the email address was attempted, if known. The string must be in the [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339) date-time format. The time must not be before 1970-01-01T00:00:00Z or more than two days in the future. For a time outside this range, MaxMind ignores the input and returns a warning. + + [Learn more about the /email/verification\_time input on our Knowledge Base.](https://support.maxmind.com/knowledge-base/articles/passing-email-inputs-minfraud) + {{}} + + {{< minfraud-schema-row key="was_verification_successful" type="request" valueType="boolean" >}} + Whether the most recent verification that the end user controls this email address was successful (e.g. by confirming a link sent to the email address). `true` if the email verification was successful, or `false` if the user failed email verification. Do not include this field if you have not performed this check. + + [Learn more about the /email/was\_verification\_successful input on our Knowledge Base.](https://support.maxmind.com/knowledge-base/articles/passing-email-inputs-minfraud) + {{}} {{}} diff --git a/content/minfraud/release-notes/2026-10-26-new-email-verification-inputs.md b/content/minfraud/release-notes/2026-10-26-new-email-verification-inputs.md new file mode 100644 index 000000000..7afa134b6 --- /dev/null +++ b/content/minfraud/release-notes/2026-10-26-new-email-verification-inputs.md @@ -0,0 +1,13 @@ ++++ +title = 'New email verification inputs' +date = 2026-10-26T16:00:00Z +draft = false ++++ + +We have released new inputs for all minFraud web service customers. They +describe the most recent verification of the email address. + +| new input | description | +| ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `email/verification_time` | The most recent date and time a verification of the email address was attempted, if known. [Learn more on our developer portal.](/minfraud/api-documentation/requests/#schema--request--email__verification_time) | +| `email/was_verification_successful` | Whether the most recent verification that the end user controls this email address was successful. [Learn more on our developer portal.](/minfraud/api-documentation/requests/#schema--request--email__was_verification_successful) |