Email Append
Email addresses for a person, from a name and US postal address.
curl -X POST https://api.1lookup.dev/v1/email-append \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"first_name":"Jordan","last_name":"Avery","address":"1200 Example Ave","city":"Austin","state":"TX"}'{
"success": true,
"data": {
"match": true,
"person": {
"first_name": "Jordan",
"last_name": "Avery"
},
"address": {
"street": "1200 Example Ave",
"city": "Austin",
"state": "TX",
"zip": "78701"
},
"emails": [
{
"email": "jordan.avery@example.com",
"validation_status": "deliverable"
},
{
"email": "javery@example.com",
"validation_status": "risky"
}
],
"email_count": 2,
"deliverable_count": 1
},
"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.
first_namestringrequiredFirst name. Example: Jordan
last_namestringrequiredLast name. Example: Avery
addressstringrequiredStreet address. Example: 1200 Example Ave
citystringrequiredCity. Example: Austin
statestringrequiredState. Example: TX
zipstringZIP code. Example: 78701
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.matchbooleanWhether at least one email was found for the person. Only matched records are charged.
data.emailsarrayThe addresses found. Each item carries the email and its validation status.
data.email_countnumberThe number of addresses returned for this record.
data.deliverable_countnumberHow many of the returned addresses validated as deliverable.
data.personobjectThe first and last name the append was matched on.
data.addressobjectThe US postal address used as the match key.
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