> ## Documentation Index
> Fetch the complete documentation index at: https://www.forager.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Forager is a REST API for B2B people, company and job post data: contact lookups (phone numbers, personal emails, work emails), person, company and job post search, and bulk data feeds.
> Server: https://api-v2.forager.ai. Send the API key in the X-API-KEY header. Most paths include {account_id}. Read FORAGER_API_KEY and FORAGER_ACCOUNT_ID from the environment; never put the key in client-side code, logs or prompts.
> To add Forager to a project, follow https://www.forager.ai/docs/guides/agent-quickstart.md. To pick an endpoint, read https://www.forager.ai/docs/guides/choose-an-endpoint.md. For end-to-end builds, see https://www.forager.ai/docs/recipes/overview.md.
> Most requests spend credits. Do not guess costs; use https://www.forager.ai/docs/api-overview/credit-pricing.md and ask the user before spending credits.
> Use only endpoints and fields defined in https://www.forager.ai/docs/openapi.yaml. Forager has no MCP server for the API yet; the /mcp endpoint on this site searches the documentation only.

# Contact enrichment with the API

> Look up a person record from a LinkedIn public identifier or Forager ID with the Person Detail Lookup API.

![Contact enrichment: an identifier returns a full person record with name, headline, roles and education](https://mintcdn.com/forager/EGsWCxLOYv1Cb__c/images/illustrations/contact-enrichment-person-record.svg?fit=max\&auto=format\&n=EGsWCxLOYv1Cb__c\&q=85\&s=b1dbdedd91cec07fbb9a3987855dcb17)

Use this when you already know who a person is and want their full record from the Forager dataset.

## Before you start

* An API key and your Account ID. See [Create an account](https://www.forager.ai/docs/api-overview/create-an-account.md).
* One identifier for the person: a LinkedIn public identifier (the slug in `linkedin.com/in/<slug>/`) or a Forager ID (`person_id`).

## Look up the person

Send a `POST` to [Person detail lookup](https://www.forager.ai/docs/openapi/people/datastorage_person_detail_lookup_create.md) with either `linkedin_public_identifier` or `person_id`.

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
curl -X POST "https://api-v2.forager.ai/api/$FORAGER_ACCOUNT_ID/datastorage/person_detail_lookup/" \
     -H "X-API-KEY: $FORAGER_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{
           "linkedin_public_identifier": "billgates"
         }'
```

Set `FORAGER_API_KEY` and `FORAGER_ACCOUNT_ID` in your shell first, as in the [quickstart](https://www.forager.ai/docs/api-overview/send-your-first-request.md). See [Authentication](https://www.forager.ai/docs/api-overview/authentication.md).

Change the identifier, or switch to the reverse lookup by email, to see the request in each language:

**POST**

Cost: . Nothing is sent from this page.

<pre />

## Read the response

The response is one person record: identity fields, `location`, `linkedin_info`, then `roles` (newest first), `educations` and the other profile lists, which are empty arrays when the profile has none. Click a field to see its type and meaning. The values are illustrative, not a real record.

. Click a field. Values are illustrative.

Types and nullability follow the OpenAPI spec; nested objects show their own fields when you click inside them.

## How the lookups fit together

Every lookup starts from something that identifies the person. The person record carries an `id`, which the phone and personal email lookups accept as `person_id`. The work email lookup does not take a `person_id`: send a LinkedIn handle, or a first name, last name and company domain.

![Enrichment flow: a LinkedIn handle, email or phone number returns a person record with an id; the id feeds the phone and personal email lookups, and a name with a company domain goes straight to the asynchronous work email lookup](https://mintcdn.com/forager/ns67u_aB3_RSoht6/images/illustrations/contact-enrichment-lookup-flow-person-id.svg?fit=max\&auto=format\&n=ns67u_aB3_RSoht6\&q=85\&s=a0737b75f068a0567d0c0bc412a1bd2e)

If you already have a LinkedIn handle or a `person_id` and only need contact data, skip the person lookup and call the contact lookup directly.

## Next steps

* You only have an email or a phone number? Use the reverse lookups: [by email](https://www.forager.ai/docs/openapi/people/datastorage_person_detail_reverse_lookup_by_email_create.md) or [by phone](https://www.forager.ai/docs/openapi/people/datastorage_person_detail_reverse_lookup_by_phone_number_create.md).
* Need contact data? See [Find phone numbers](https://www.forager.ai/docs/guides/find-phone-numbers.md) and [Bulk work emails](https://www.forager.ai/docs/guides/bulk-work-emails.md).
* Check [Credit pricing](https://www.forager.ai/docs/api-overview/credit-pricing.md) before running this at volume.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.