Skip Trace
Phone numbers and emails for a person, from a name and US mailing address.
curl -X POST https://api.1lookup.dev/v1/skip-trace \
-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"
},
"phones": [
{
"number": "+15125550142",
"line_type": "mobile",
"dnc": false,
"confidence": "high"
},
{
"number": "+15125550117",
"line_type": "landline",
"dnc": true,
"confidence": "medium"
},
{
"number": "+17375550163",
"line_type": "voip",
"dnc": false,
"confidence": "low"
}
],
"emails": [
{
"email": "jordan.avery@example.com",
"confidence": "high"
},
{
"email": "javery@example.com",
"confidence": "medium"
}
],
"counts": {
"phones": 3,
"emails": 2
}
},
"meta": {
"credits_used": 5,
"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 a record was found for the name and address. A false result is not billed.
data.phonesarrayA list ordered by confidence. Each item has the number, its line type, a DNC flag and a confidence level.
data.emailsarrayEmails tied to the person, each with a confidence level.
data.counts.phonesnumberHow many phone numbers the match returned.
data.counts.emailsnumberHow many email addresses the match returned.
data.personobjectThe name on the matched record, so you can confirm it is the person you sent.
data.addressobjectThe mailing address the match was made on.
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
5 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