---
title: "Business Email to SHA256"
method: POST
path: "/business_email_to_sha256"
tags: ["Get Ad Audience"]
---

# Business Email to SHA256

`POST /business_email_to_sha256`

## Request

- Base URL: `https://api.moltsets.com/api/v1/tools`
- URL: `https://api.moltsets.com/api/v1/tools/business_email_to_sha256`
- Auth: HTTP bearer

The Business Email to SHA256 API converts a business email address into a SHA256-hashed personal email address, for privacy-safe identity resolution and paid advertising audience matching.

The hash it returns can be uploaded directly to Meta, Google, LinkedIn, TikTok, and other ad platforms that support customer match or custom audience workflows. Use this to retarget known contacts across their personal devices without exposing raw personal email data.

**Use this endpoint to:**
- Build customer match audiences for Meta, Google, LinkedIn, or TikTok
- Retarget contacts on their personal devices without exposing raw email addresses
- Bridge business contacts to privacy-safe advertising identifiers

**Need multiple SHA256s?**
This API returns only ONE SHA256. If you are running ads and want MULTIPLE SHA256's, and are willing to spend at least $10k/yr, please <a href="https://moltsets.com/data-sales/?product=email-to-sha256" target="_blank" rel="noopener">click here</a> and talk to our data team.

**Fair Use Policy:**
This API is subject to our <a href="https://moltsets.com/fair-use-policy-enrichment/" target="_blank" rel="noopener">Fair Use Policy for Enrichment</a>.

**Plan Availability:**
This endpoint is not available on the \$397 / month and \$997 / month plans. Calls from those plans return `403` with `plan_restricted`. It is a plan condition, so retrying or topping up tokens does not clear it.

**Response fields:**
`personal_email_SHA256` holds one string, not an array. When there's no data, the field is left out of `results`.

**Outcomes:**
A lookup that finds nothing is not an error. It returns HTTP `200` with `status: "not_found"`, empty or null `results`, and the usual `metadata` — and costs no tokens, though it still counts as one request against your Fair Use requests limit. Read `status`, not the HTTP code, to tell a hit from a miss. The API's only `404` is an unknown or retired tool name.

## Headers

- `User-Agent` string, required

## Request body

- object
  - `email` string: Business email address.

## Response `200`

Success

## Other responses

- `401`: Unauthorized
- `402`: Payment Required — insufficient tokens
- `403`: Forbidden — missing `User-Agent` header, tool not on the plan, or account inactive
- `422`: Invalid Input — malformed body, or a parameter is missing, malformed, or outside its allowed values
- `429`: Too Many Requests — rate limit or Fair Use window exhausted
- `500`: Internal Server Error — the call could not complete. Usually the endpoint is temporarily unavailable, but an oversized request can also cause it. Retry with a smaller request first; the MoltSets team is alerted automatically.

---

[API](https://skmtc.dev/moltsets/apis/moltsets-api.md) - [All operations](https://skmtc.dev/moltsets/apis/moltsets-api/llms.txt) - [OpenAPI document](https://skmtc.dev/moltsets/apis/moltsets-api/revisions/b116df68bd90?raw)