Check a freelancer's claimed work history at sign-up

Compare a new freelancer's or expert's claimed employers and titles with their professional profile, so the marketplace reviews mismatches before the profile goes live.

Get a free API key + $5 Get a sample run

Free API key
No credit card
Run your sample

Tools named: LinkedIn

Uses POST /person_detail_reverse_lookup/by_email/, POST /person_detail_lookup/ · Reverse email lookup API reference

What it costs: Charged per request: credit pricing.

Reverse email lookup
Person enrichment
API
Embedded in a platform
HR tech

How the data flows

3 inputs → Reverse email lookup + Person enrichment → 3 fields sample data

01 · Inputs

sign-up email

linkedin.com/in/lee-sampler

claimed experience

linkedin.com/in/lee-sampler

LinkedIn URL

linkedin.com/in/lee-sampler

02 · Forager

Reverse email lookup + Person enrichment POST /person_detail_reverse_lookup/by_email/

Match found

03 · Outputs

Lee SamplerSenior Software Engineer · Sample Labs

matched profile: /in/lee-sampler
roles with dates: Senior Software Engineer
name: Lee Sampler
mobile: +1 (312) 555-0107
work email: lee@samplelabs.example
company: Sample Labs

3 fields in the responseexample data

Steps

Resolve the sign-up email with POST /person_detail_reverse_lookup/by_email/
If they also give a LinkedIn URL, fetch the profile with POST /person_detail_lookup/ (linkedin_public_identifier)
Compare claimed employers, titles and dates with roles (organization_name, role_title, start_date, end_date)
Approve matching profiles and route mismatches to a reviewer

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. Resolve the sign-up email with POST
# /person_detail_reverse_lookup/by_email/
r1 = requests.post(f"{BASE}/person_detail_reverse_lookup/by_email/", headers=HEADERS, json=body)

# 2. If they also give a LinkedIn URL, fetch the profile with POST
# /person_detail_lookup/ (linkedin_public_identifier)
r2 = requests.post(f"{BASE}/person_detail_lookup/", headers=HEADERS, json=body)

# 3. Compare claimed employers, titles and dates with roles
# (organization_name, role_title, start_date, end_date)

# 4. Approve matching profiles and route mismatches to a reviewer

# 1. POST /person_detail_reverse_lookup/by_email/
curl -X POST \
  https://api-v2.forager.ai/api/{account_id}/datastorage/person_detail_reverse_lookup/by_email/ \
  -H "X-API-KEY: $FORAGER_KEY" \
  -H "Content-Type: application/json" \
  -d @request.json

# 2. 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

Generated from the recipe stepsRequest fields: API reference

Run it yourself: Reverse email lookup API reference

Get a free API key + $5 Get a sample run

Free API key
No credit card
Run your sample

Inputs and outputs

Inputs	Outputs
sign-up email	`matched profile`
claimed experience	`roles with dates`
LinkedIn URL (optional)	`match or mismatch flag`

Questions about this recipe

How can a freelance marketplace check that a sign-up's work history is real?

Resolve the sign-up email with POST /person_detail_reverse_lookup/by_email/. If they also give a LinkedIn URL, fetch the profile with POST /person_detail_lookup/ (linkedin_public_identifier).

What does it cost to check a freelancer's claimed work history at sign-up?

Reverse email lookup: 5 credits per request, charged whether or not data comes back. Person enrichment: 1 credit per request, charged whether or not data comes back. Growth's 8,250 monthly credits cover 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 claimed experience, LinkedIn URL (optional) and sign-up email. You get back match or mismatch flag, matched profile and roles with dates, as JSON. You also need a Forager API key, which comes with a free account.

Which API returns someone's past employers from their email?

This recipe uses Forager Reverse email lookup and Person enrichment. Reverse email lookup: Turn an email address into a full person profile: name, title, company, location and social links. Compare a new freelancer's or expert's claimed employers and titles with their professional profile, so the marketplace reviews mismatches before the profile goes live.

Is there a free way to try Forager on this workflow?

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 freelancer or expert signs up and submits their experience. Clients see vetted profiles, and the review team spends its time on the sign-ups that do not match.

Which Forager products does this recipe use?

Reverse email lookup and person enrichment. Reverse email lookup: turn an email address into a full person profile: name, title, company, location and social links. Person enrichment: a full professional profile for a person from a LinkedIn URL, email or phone: experience, education, skills and contact channels.

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.

Which tools can run this workflow?

Native in Clay, 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: resolve the sign-up email with POST /person_detail_reverse_lookup/by_email/, if they also give a LinkedIn URL, fetch the profile with POST /person_detail_lookup/ (linkedin_public_identifier), compare claimed employers, titles and dates with roles (organization_name, role_title, start_date, end_date) and approve matching profiles and route mismatches to a reviewer.

Is there a contract or minimum commitment?

No contract to start: 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.

Can we show Forager data inside our product?

Yes, under platform terms. Self-serve plans cover internal use by your own team. Showing Forager data to your users, or passing records on, is licensed separately: talk to sales about volume and which fields your users need to see.

Check a freelancer's claimed work history at sign-up

How the data flows

Steps

Inputs and outputs

Questions about this recipe

How can a freelance marketplace check that a sign-up's work history is real?

What does it cost to check a freelancer's claimed work history at sign-up?

What do I need to run this recipe, and what comes back?

Which API returns someone's past employers from their email?

Is there a free way to try Forager on this workflow?

When should I run this workflow?

Which Forager products does this recipe use?

How accurate is Forager data?

Which tools can run this workflow?

How many steps is this workflow?

Is there a contract or minimum commitment?

Can we show Forager data inside our product?

More recipes for talent marketplaces

Help job seekers reach the hiring manager behind a job posting

Prospect plant and warehouse managers for an on-demand staffing marketplace

Recommend live job openings to candidates on a talent marketplace

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

Put people, company and job data your users can act on inside your product