Skip to main content
POST
/
utility
/
hash
/
email
Hash email address for privacy
curl --request POST \
  --url https://api.datalegion.ai/utility/hash/email \
  --header 'API-Key: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "email": "Jane.Doe+tag@gmail.com"
}
'
{
  "email": "Jane.Doe+tag@gmail.com",
  "normalized_email": "janedoe@gmail.com",
  "hashes": {
    "sha256": "d6117306485ed0e50afab3ac871e98f81699151f30281527d63ff5f233656c69",
    "sha1": "3e12c6d13e5c00d46fee94de65239ce9c5e7bc25",
    "md5": "a9601f3839e5d5da764c1861a5e1daf6"
  }
}

​
How It Works

Pass an email address and receive SHA-256, SHA-1, and MD5 hashes of the normalized email. The email is cleaned (lowercased, Gmail dots removed, plus tags stripped) before hashing. Use the returned hash with the email_hash field in Person Enrichment for privacy-safe lookups — you never need to send the raw email address.

​
Workflow

  1. Hash the email using this endpoint
  2. Store or transmit only the hash
  3. Use the hash with email_hash in person enrichment

Authorizations

​
API-Key
string
header
required

Body

application/json

Request model for email hashing.

​
email
string
required

Email address to hash

Response

Success - email hashed

Response model for email hashing.

​
email
string
required

Original email address

​
normalized_email
string
required

Normalized email address (used for hashing)

​
hashes
Hashes · object
required

Hash values keyed by algorithm (sha256, sha1, md5)