Forager: Person Contacts Lookup Personal Emails

The Person Personal Emails Lookup endpoint retrieves personal email addresses associated with an individual in the Forager dataset.

Tool ID: forager_person_contacts_lookup_personal_emails

Run this action

Use the TypeScript SDK for a single call. Put ctx.tools.execute(...) inside a Play when the call should be durable, scheduled, or run across a CSV.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'forager_person_contacts_lookup_personal_emails',
  {
    "person_id": 123,
    "linkedin_public_identifier": "https://www.linkedin.com/in/jane-doe"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute forager_person_contacts_lookup_personal_emails --input '{
  "person_id": 123,
  "linkedin_public_identifier": "https://www.linkedin.com/in/jane-doe"
}' --json

Example response

The SDK exposes this shape at result.toolResponse.raw. Values below are representative.

{
  "data": [
    {
      "email": "jane.doe@example.com",
      "email_type": "jane.doe@example.com",
      "validation_status": "valid"
    }
  ]
}

Use deepline tools get forager_person_contacts_lookup_personal_emails --json for the latest machine-readable contract.

Input reference

Person info request serializer.

Name	Type	Required	Default	Details
`payload.person_id`	`integer`	No	—	—
`payload.linkedin_public_identifier`	`string`	No	—	LinkedIn organization “Public identifier/Slug/ID” - “linkedin.com/in/!slug!/”.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`array`	Yes	—	Provider response payload.
`result.data[].email`	`string`	Yes	—	Format: `email`.
`result.data[].email_type`	`string`	Yes	—	—
`result.data[].validation_status`	`"valid" \| "risky" \| "invalid" \| "unknown"`	Yes	—	* `valid` - Valid * `risky` - Risky * `invalid` - Invalid * `unknown` - Unknown Allowed: `valid`, `risky`, `invalid`, `unknown`.
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: per_result (per result).
Estimated Deepline credits: 1.56 per pricing unit.

Get started

Build and automate

Common workflows

Data and integrations

Reference

Forager: Person Contacts Lookup Personal Emails

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation