$5 free Limited time. Sign up to activate. Get your $5 →
Free tool

What data can I get for this record?

Start from what you already have. The explorer lists the endpoints that take it, what each costs in credits, the fields that come back and a sample response, with a link to the reference page for each.

What do you have?

Every sample here is fictional (example domains, 555 numbers, made-up names). Field names are the API reference’s; which fields are filled depends on the record.

You have a LinkedIn URL linkedin.com/in/priya-example

The handle at the end of the URL is the linkedin_public_identifier every person endpoint takes. Four lookups apply, each billed on its own.

  1. Person profile lookup

    1 credit · charged per request

    POST /person_detail_lookup/

    You send
    {
      "linkedin_public_identifier": "priya-example"
    }
    Fields that come back
    • id
    • full_name
    • first_name
    • last_name
    • headline
    • location[]
    • linkedin_info
    • roles[]
    • educations[]
    • skills[]
    • certifications[]
    • languages[]
    Sample response (fictional)
    {
      "id": 48213907,
      "full_name": "Priya Example",
      "first_name": "Priya",
      "last_name": "Example",
      "headline": "Head of Revenue Operations at Northwind Example Labs",
      "location": [
        {
          "id": 4671,
          "name": "Austin, Texas, United States"
        }
      ],
      "linkedin_info": {
        "public_identifier": "priya-example",
        "public_profile_url": "https://www.linkedin.com/in/priya-example/"
      },
      "roles": [
        {
          "role_title": "Head of Revenue Operations",
          "organization_name": "Northwind Example Labs",
          "start_date": "2023-02",
          "end_date": null,
          "is_current": true
        }
      ],
      "educations": [
        {
          "school_name": "Example State University",
          "degree": "BSc",
          "field_of_study": "Economics",
          "end_date": "2014"
        }
      ],
      "skills": [
        {
          "name": "Revenue operations"
        },
        {
          "name": "Salesforce administration"
        }
      ]
    }

    The id and linkedin_info.public_identifier feed every contact lookup.

    Person enrichment API reference (opens in a new tab)

  2. Mobile number lookup

    15 credits · charged only when data comes back

    POST /person_contacts_lookup/phone_numbers/

    You send
    {
      "linkedin_public_identifier": "priya-example"
    }
    Fields that come back
    • phone_number
    Sample response (fictional)
    [
      {
        "phone_number": "+15550100142"
      }
    ]

    Mobile numbers API reference (opens in a new tab)

  3. Work email lookup

    5 credits · charged only when data comes back

    POST /person_contacts_lookup/work_emails/

    You send
    {
      "linkedin_public_identifier": "priya-example"
    }
    Fields that come back
    • job_id
    • status
    • emails[]
    • person_id
    • submitted_lookup
    • error_code
    Sample response (fictional)
    {
      "job_id": "6f1c2a0e-0000-4000-8000-000000000042",
      "status": "completed",
      "emails": [
        "priya@northwind.example"
      ],
      "person_id": 48213907,
      "error_code": null
    }

    The lookup runs as a job: submit, then read the result at status_check_url or receive it on your webhook_url.

    Work emails API reference (opens in a new tab)

  4. Personal email lookup

    5 credits · charged only when data comes back

    POST /person_contacts_lookup/personal_emails/

    You send
    {
      "linkedin_public_identifier": "priya-example"
    }
    Fields that come back
    • email
    • email_type
    • validation_status
    Sample response (fictional)
    [
      {
        "email": "priya.example@example.com",
        "email_type": "personal",
        "validation_status": "valid"
      }
    ]

    Personal emails API reference (opens in a new tab)

You have an email address priya.example@example.com

An email resolves to the person behind it. The profile that comes back carries the handle and person ID, so the contact lookups follow from there.

  1. Reverse email lookup

    5 credits · charged per request

    POST /person_detail_reverse_lookup/by_email/

    You send
    {
      "email": "priya.example@example.com"
    }
    Fields that come back
    • id
    • full_name
    • first_name
    • last_name
    • headline
    • location[]
    • linkedin_info
    • roles[]
    • educations[]
    • skills[]
    • certifications[]
    • languages[]
    Sample response (fictional)
    {
      "id": 48213907,
      "full_name": "Priya Example",
      "first_name": "Priya",
      "last_name": "Example",
      "headline": "Head of Revenue Operations at Northwind Example Labs",
      "location": [
        {
          "id": 4671,
          "name": "Austin, Texas, United States"
        }
      ],
      "linkedin_info": {
        "public_identifier": "priya-example",
        "public_profile_url": "https://www.linkedin.com/in/priya-example/"
      },
      "roles": [
        {
          "role_title": "Head of Revenue Operations",
          "organization_name": "Northwind Example Labs",
          "start_date": "2023-02",
          "end_date": null,
          "is_current": true
        }
      ],
      "educations": [
        {
          "school_name": "Example State University",
          "degree": "BSc",
          "field_of_study": "Economics",
          "end_date": "2014"
        }
      ],
      "skills": [
        {
          "name": "Revenue operations"
        },
        {
          "name": "Salesforce administration"
        }
      ]
    }

    Then pass linkedin_info.public_identifier (or id as person_id) to the mobile, work email and personal email lookups.

    Reverse email lookup API reference (opens in a new tab)

  2. Mobile number lookup

    15 credits · charged only when data comes back

    POST /person_contacts_lookup/phone_numbers/

    You send
    {
      "person_id": 48213907
    }
    Fields that come back
    • phone_number
    Sample response (fictional)
    [
      {
        "phone_number": "+15550100142"
      }
    ]

    Mobile numbers API reference (opens in a new tab)

  3. Work email lookup

    5 credits · charged only when data comes back

    POST /person_contacts_lookup/work_emails/

    You send
    {
      "person_id": 48213907
    }
    Fields that come back
    • job_id
    • status
    • emails[]
    • person_id
    • submitted_lookup
    • error_code
    Sample response (fictional)
    {
      "job_id": "6f1c2a0e-0000-4000-8000-000000000042",
      "status": "completed",
      "emails": [
        "priya@northwind.example"
      ],
      "person_id": 48213907,
      "error_code": null
    }

    The lookup runs as a job: submit, then read the result at status_check_url or receive it on your webhook_url.

    Work emails API reference (opens in a new tab)

You have a name and a company domain Priya Example, northwind.example

A first name, last name and company domain is enough for a work email. To reach the other lookups, find the person first with a search.

  1. Work email lookup

    5 credits · charged only when data comes back

    POST /person_contacts_lookup/work_emails/

    You send
    {
      "first_name": "Priya",
      "last_name": "Example",
      "domain": "northwind.example"
    }
    Fields that come back
    • job_id
    • status
    • emails[]
    • person_id
    • submitted_lookup
    • error_code
    Sample response (fictional)
    {
      "job_id": "6f1c2a0e-0000-4000-8000-000000000042",
      "status": "completed",
      "emails": [
        "priya@northwind.example"
      ],
      "person_id": 48213907,
      "error_code": null
    }

    The lookup runs as a job: submit, then read the result at status_check_url or receive it on your webhook_url.

    Work emails API reference (opens in a new tab)

  2. People search

    1 credit · charged per request

    POST /person_role_search/

    You send
    {
      "person_name": "Priya Example",
      "organization_domains": [
        "northwind.example"
      ]
    }
    Fields that come back
    • search_results[].role_title
    • search_results[].is_current
    • search_results[].organization
    • search_results[].person
    • total_search_results
    Sample response (fictional)
    {
      "search_results": [
        {
          "role_title": "Head of Revenue Operations",
          "is_current": true,
          "organization": {
            "id": 1180422,
            "name": "Northwind Example Labs",
            "domain": "northwind.example"
          },
          "person": {
            "id": 48213907,
            "full_name": "Priya Example",
            "headline": "Head of Revenue Operations at Northwind Example Labs",
            "linkedin_info": {
              "public_identifier": "priya-example"
            }
          }
        }
      ],
      "total_search_results": 1
    }

    The person.id and linkedin_info.public_identifier in a result feed the mobile and email lookups.

    People search API reference (opens in a new tab)

  3. Mobile number lookup

    15 credits · charged only when data comes back

    POST /person_contacts_lookup/phone_numbers/

    You send
    {
      "person_id": 48213907
    }
    Fields that come back
    • phone_number
    Sample response (fictional)
    [
      {
        "phone_number": "+15550100142"
      }
    ]

    Mobile numbers API reference (opens in a new tab)

You have a company domain northwind.example

A domain finds the company record, the people who work there and the roles it is hiring for.

  1. Company search

    1 credit · charged per request

    POST /organization_search/

    You send
    {
      "domains": [
        "northwind.example"
      ]
    }
    Fields that come back
    • id
    • name
    • legal_name
    • domain
    • website
    • founded_date
    • employees_range
    • employees_amount
    • location[]
    • linkedin_info
    • finance_info
    • keywords[]
    • found_funding_events[]
    • found_job_post_events[]
    Sample response (fictional)
    {
      "search_results": [
        {
          "id": 1180422,
          "name": "Northwind Example Labs",
          "domain": "northwind.example",
          "website": "https://northwind.example",
          "founded_date": "2016-05-01",
          "employees_range": "51-200",
          "employees_amount": 140,
          "location": [
            {
              "id": 4671,
              "name": "Austin, Texas, United States"
            }
          ],
          "linkedin_info": {
            "public_identifier": "northwind-example-labs"
          },
          "finance_info": {
            "revenue": 18000000
          },
          "keywords": [
            {
              "name": "revenue intelligence"
            },
            {
              "name": "b2b saas"
            }
          ]
        }
      ],
      "total_search_results": 1
    }

    The id is the organization_ids value the job postings search takes.

    Company enrichment API reference (opens in a new tab)

  2. People search

    1 credit · charged per request

    POST /person_role_search/

    You send
    {
      "organization_domains": [
        "northwind.example"
      ],
      "role_title": "revenue operations",
      "role_is_current": true
    }
    Fields that come back
    • search_results[].role_title
    • search_results[].person
    • search_results[].organization
    • total_search_results
    Sample response (fictional)
    {
      "search_results": [
        {
          "role_title": "Head of Revenue Operations",
          "is_current": true,
          "person": {
            "id": 48213907,
            "full_name": "Priya Example",
            "linkedin_info": {
              "public_identifier": "priya-example"
            }
          },
          "organization": {
            "id": 1180422,
            "name": "Northwind Example Labs",
            "domain": "northwind.example"
          }
        }
      ],
      "total_search_results": 14
    }

    People search API reference (opens in a new tab)

  3. Job postings search

    2 credits · charged per request

    POST /job_search/

    You send
    {
      "organization_ids": [
        1180422
      ],
      "is_active": true
    }
    Fields that come back
    • search_results[].title
    • search_results[].date_featured
    • search_results[].organization
    • search_results[].location[]
    • search_results[].is_remote
    • search_results[].url
    • total_search_results
    Sample response (fictional)
    {
      "search_results": [
        {
          "title": "Senior Data Engineer",
          "date_featured": "2026-10-14",
          "organization": {
            "id": 1180422,
            "name": "Northwind Example Labs",
            "domain": "northwind.example"
          },
          "location": [
            {
              "name": "Austin, Texas, United States"
            }
          ],
          "is_remote": true,
          "is_active": true,
          "url": "https://northwind.example/careers/senior-data-engineer"
        }
      ],
      "total_search_results": 3
    }

    Job postings API reference (opens in a new tab)

Requests go to https://api-v2.forager.ai/api/{account_id}/datastorage with your API key in the X-API-KEY header. Search filters such as locations, industries and skills take IDs from the autocomplete endpoints, not free text.

Run these on your own records

  • $5 free credits
  • No credit card
  • Run your sample
Start building

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

Send us a list. We run it, show you what we find, then talk volume and terms.

  • $5 free credits
  • No credit card
  • Run your sample
Platforms and teams that build on Forager
  • Clay
  • Juicebox
  • Nooks
  • Andela
  • HubSpot
  • SeekOut