Reverse Email Lookup
The name, phone, address and employer behind an email address.
curl -X POST https://api.1lookup.dev/v1/reverse-email-lookup \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"email":"jane.doe@example.com"}'{
"success": true,
"data": {
"email": "jane.doe@example.com",
"match": true,
"person": {
"full_name": "Jane Doe",
"first_name": "Jane",
"last_name": "Doe"
},
"phone": "+13035550118",
"address": {
"street": "77 Example Blvd",
"city": "Denver",
"state": "CO",
"zip": "80202",
"country": "US"
},
"employment": {
"company": "Fabrikam Health",
"title": "Operations Manager"
}
},
"meta": {
"credits_used": 10,
"credits_remaining": 999,
"cached": false,
"request_id": "req_8f3a2c1e9b7d"
}
}Authorization
Authorizationstring<bearer>requiredYour API key as a Bearer token. Live keys start with 1lk_live_. Test keys start with 1lk_test_ and return this endpoint's sample response without spending credits. See authentication.
Body
Send the fields as a JSON object with Content-Type: application/json.
emailstring<email>requiredEmail address. Example: jane.doe@example.com
freshbooleanSkip the 7-day cache and run a new lookup. Charged as a normal lookup.
referencestringYour own identifier, echoed back in meta and shown in lookup history.
Response
A 200 response carries the result in data and the cost of the call in meta. These are the fields most integrations read.
successbooleantrue when the lookup ran.
data.matchbooleantrue when the address is associated with a known person.
data.person.full_namestringThe full name tied to the email address.
data.phonestringA phone number for the person, where one is known.
data.addressobjectStreet, city, state, ZIP and country, where a postal address is on file.
data.employment.companystringThe company the person works for, where known.
data.employment.titlestringThe person's title at that employer, where known.
meta.credits_usednumberCredits charged for this call.
meta.credits_remainingnumberYour balance after the call.
meta.cachedbooleantrue when the result came from the 7-day cache.
meta.request_idstringQuote this when you contact support.
Errors
A failed request returns success: false with an error object, and is never charged. The full list is on the errors page.
| HTTP | Code | Meaning |
|---|---|---|
| 401 | unauthorized | The key is missing, malformed or revoked. |
| 402 | insufficient_credits | Your credits are used up and pay as you go is off or at its limit. |
| 422 | invalid_input | A field is missing or malformed. The field property names it. |
| 429 | rate_limited | Too many requests for this key. Wait for the Retry-After interval. |
| 500 | internal_error | Something failed on our side. Safe to retry. |
| 503 | source_unavailable | An upstream source did not answer in time. Safe to retry. |
Billing
10 credits / match. Charged only when a match is found. Errors are never charged, and repeating the same input within 7 days is served from cache at no charge.
Product overview and use cases