Reverse Email Lookup
Identify a professional from a valid work email.
POST
/v2/enrichment/email-to-personRequest
curl -X POST "https://moltsetz.vercel.app/v2/enrichment/email-to-person" \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"email": "person@company.com"
}'Body
| Field | Type | Required | Description and limits |
|---|---|---|---|
email | string | Required | Email address to resolve.Valid email; maximum 254 characters |
Pagination
This endpoint is not paginated.
Credits
One request credit is recorded only when this endpoint returns a 2xx response. Authentication, validation, rate-limit, and not-found responses do not consume a credit.
Response
| Field | Type | Description |
|---|---|---|
found | boolean | Whether a matching record was found. |
person | object | Person profile when found. |
Example response
{
"found": true,
"person": {
"full_name": "Example Person"
}
}Errors
| Status | Code | When |
|---|---|---|
422 | INVALID_INPUT | A required value is missing, malformed, or outside its documented limits. |
404 | NOT_FOUND | The input is valid but no matching record exists. |
401 | UNAUTHORIZED | The x-api-key header is missing or invalid. |
402 | CREDITS_EXHAUSTED | A limited plan has no request credits remaining. |
405 | METHOD_NOT_ALLOWED | The endpoint is called with an unsupported HTTP method. |
429 | RATE_LIMIT_EXCEEDED | The API key exceeds its plan-wide requests-per-second limit. |
500 | DATA_SERVICE_ERROR | The data service cannot complete the request. |
{
"success": false,
"error": {
"code": "INVALID_INPUT",
"message": "A field-specific validation message"
}
}