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

# Work Emails

> Find and verify a person's work email: single or bulk lookups, polling for results, optional webhook.

Find and verify a person's work email address. Submit a lookup (single or bulk), poll the job for its result, and optionally receive the result by webhook when the job completes.

## How a lookup runs

Work email lookups are asynchronous. The submit call answers `202` at once with a job id and a `status_check_url`. Poll that URL until `status` is `completed` or `failed`, or pass a `webhook_url` and Forager POSTs the result to it when the job finishes. Polling is free.

Step through one single lookup, from the `202` to a terminal status (illustrative payloads):

Back
Next

* **Single lookup:** `status` moves through `queued`, `running` and `awaiting_provider` to `completed` or `failed`. A completed job has `result` set to `found` or `not_found`; a failed one has an `error_code`.
* **Bulk lookup:** the submit returns a `batch_id`. The batch `status` is `queued`, `running`, `completed` or `failed`, and `results` stays empty until the batch is `completed`, then holds one result per submitted lookup in the order you sent them.

## Endpoints

* [POST /api/v2/\{account\_id}/datastorage/person\_contacts\_lookup/work\_emails/](https://www.forager.ai/docs/openapi/work-emails/v2_datastorage_person_contacts_lookup_work_emails_create.md): Single work email lookup
* [GET /api/v2/\{account\_id}/datastorage/person\_contacts\_lookup/work\_emails/\{job\_id}/](https://www.forager.ai/docs/openapi/work-emails/v2_datastorage_person_contacts_lookup_work_emails_retrieve.md): Single work email lookup result
* [POST /api/v2/\{account\_id}/datastorage/person\_contacts\_lookup/work\_emails/bulk/](https://www.forager.ai/docs/openapi/work-emails/v2_datastorage_person_contacts_lookup_work_emails_bulk_create.md): Bulk work email lookup
* [GET /api/v2/\{account\_id}/datastorage/person\_contacts\_lookup/work\_emails/bulk/\{batch\_id}/](https://www.forager.ai/docs/openapi/work-emails/v2_datastorage_person_contacts_lookup_work_emails_bulk_retrieve.md): Bulk work email lookup status and results

## Build a single lookup

Identify the person by name and company domain, or by LinkedIn public identifier, and copy the submit request. Nothing is sent from this page.

**POST**

Cost: . Nothing is sent from this page.

<pre />

## Read a result

Polling the `status_check_url` returns the job. `status` says how far it got and `result` what it concluded. Click a field to see its type. The values are illustrative.

. Click a field. Values are illustrative.

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

## Credits

Each operation page shows its credit cost. See [API credits and pricing](https://www.forager.ai/docs/api-overview/credit-pricing.md) for the full table.


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