Score a contact database's freshness by checking each person's current employer
Give a data-validation or data-hygiene product a check that tells customers which contacts have left the company they are stored against, and the new work email where one exists.
- Free API key
- No credit card
- Run your sample
Uses POST /person_detail_lookup/ · Person enrichment API reference
What it costs: 5 credits per email found. A mobile or email lookup that returns nothing costs 0 credits. Enrichment and search are charged per request: credit pricing.
- Person enrichment
- Work emails
- API
- Data reseller
- B2B data providers
How the data flows
POST /person_detail_lookup/ - current employer
- Example Inc.
- new work email
- kim@example.com
- name
- Kim Exemplar
- title
- VP Revenue Operations
- mobile
- +1 (416) 555-0186
Steps
- Look up each contact with
POST /person_detail_lookup/(linkedin_public_identifier) - Compare the current role (
is_current, organization.domain) with the stored company - For people who moved, request the new address via
/person_contacts_lookup/work_emails/(linkedin_public_identifier) - Return a freshness score per list and a moved, current or unknown status per row
import json, os, requests BASE = "https://api-v2.forager.ai/api/{account_id}/datastorage" HEADERS = {"X-API-KEY": os.environ["FORAGER_KEY"]} body = json.load(open("request.json")) # request fields: see the API reference # 1. Look up each contact with POST /person_detail_lookup/ # (linkedin_public_identifier) r1 = requests.post(f"{BASE}/person_detail_lookup/", headers=HEADERS, json=body) # 2. Compare the current role (is_current, organization.domain) with the # stored company # 3. For people who moved, request the new address via # /person_contacts_lookup/work_emails/ (linkedin_public_identifier) # 4. Return a freshness score per list and a moved, current or unknown # status per row
# 1. POST /person_detail_lookup/ curl -X POST \ https://api-v2.forager.ai/api/{account_id}/datastorage/person_detail_lookup/ \ -H "X-API-KEY: $FORAGER_KEY" \ -H "Content-Type: application/json" \ -d @request.json
Run it yourself: Person enrichment API reference
- Free API key
- No credit card
- Run your sample
Inputs and outputs
| Inputs | Outputs |
|---|---|
| contact list with LinkedIn URLs | current employer |
| stored company domain | moved flag |
new work_email | |
list freshness score |
Questions about this recipe
How can I check whether contacts in a list still work at their company?
Compare the current role (is_current, organization.domain) with the stored company. For people who moved, request the new address via /person_contacts_lookup/work_emails/ (linkedin_public_identifier).
What does it cost to score a contact database's freshness by checking each person's current employer?
Person enrichment: 1 credit per request, charged whether or not data comes back. Work emails: 5 credits per work email found, and a work email lookup that finds nothing costs 0 credits. Growth's 8,250 monthly credits cover 1,650 emails or 8,250 person enrichments, or a mix. Self-serve plans are Starter, Growth, Pro and Scale. See plans and prices
What do I need to run this recipe, and what comes back?
You send contact list with LinkedIn URLs and stored company domain. You get back current employer, list freshness score, moved flag and new work_email, as JSON. You also need a Forager API key, which comes with a free account.
Is there an API to score contact data decay?
This recipe uses Forager Person enrichment and Work emails. Person enrichment: A full professional profile for a person from a LinkedIn URL, email or phone: experience, education, skills and contact channels. Give a data-validation or data-hygiene product a check that tells customers which contacts have left the company they are stored against, and the new work email where one exists.
Can I test person enrichment for free?
Yes. Create a free account at app.forager.ai: it comes with $5 in free credits and an API key, and there is no credit card to sign up. Run it on records you already know, or book a demo and send us a list: we run it and show you what we find.
When should I run this workflow?
When a customer uploads a contact list for validation, or a scheduled hygiene run starts. Customers see how stale a list is before they send to it, and get the people who moved back at their new company.
Which Forager products does this recipe use?
Person enrichment and work emails. Person enrichment: a full professional profile for a person from a LinkedIn URL, email or phone: experience, education, skills and contact channels. Work emails: verified work email addresses for a person at their current employer.
How accurate is Forager data?
The test that counts is your own: send a list of profiles you care about. We run it and show you what we find, number by number, so you can measure hit rate and connect rate yourself.
How do I detect job changes in a contact list?
Look up each contact with POST /person_detail_lookup/ (linkedin_public_identifier). For people who moved, request the new address via /person_contacts_lookup/work_emails/ (linkedin_public_identifier).
Which tools can run this workflow?
Native in Clay and Zapier, partner-built in Deepline and Cargo and called through the API from Make, n8n and your own code. Or call the endpoints in the steps above from your own code with one API key.
How many steps is this workflow?
4 steps: look up each contact with POST /person_detail_lookup/ (linkedin_public_identifier), compare the current role (is_current, organization.domain) with the stored company, for people who moved, request the new address via /person_contacts_lookup/work_emails/ (linkedin_public_identifier) and return a freshness score per list and a moved, current or unknown status per row.
Do I need a subscription?
Not to test: a free account comes with $5 in credits. To keep using Forager, choose a monthly or yearly plan. Monthly plans cancel anytime and unused credits roll over; yearly plans grant all credits upfront and cost 10% less. Larger volumes are agreed with our team.
Written answers are not available right now. The matching pages above still help, or book a demo and ask the team.
- $5 free credits
- No credit card
- Run your sample
More recipes for data validation
-
Add a phone-validation layer to a contact-data product
-
Check that a personal email belongs to the expected person
-
Detect CRM contacts who changed jobs and alert on moved champions
-
Back a sales-intelligence database with an additional mobile source
-
Build natural-language candidate search on a licensed people feed
-
Offer mobile and email enrichment as native actions in a GTM workflow builder