Skip to main content
POST
/
utility
/
hash
/
email
Hash email address for privacy
curl --request POST \
  --url https://api.example.com/utility/hash/email \
  --header 'API-Key: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "email": "john.doe@example.com"
}
'
{
  "email": "john.doe@example.com",
  "normalized_email": "johndoe@example.com",
  "hashes": {
    "sha256": "836f82db99121b3481011f16b49dfa5fbc714a0d1b1b9f784a1ebbbf5b39577f",
    "sha1": "e52e4e1fb89e82a3a9b5c2e1d8f3a7b6c4d5e6f7",
    "md5": "a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6"
  }
}

​
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)