# Work Email and Phone API. Pay per record.

> A person's work email and mobile number as JSON, by LinkedIn handle. Ask for email, phone or both. Pay only for values found.

Canonical: https://apiforagents.dev/platforms/contacts/work-email-and-phone-api · Updated 2026-10-21

Send a LinkedIn /in/ handle or profile URL and get back the person's work email, mobile number, or both. Up to ten people per call, billed per person and per part, with an optional check on every email before it counts.

- Price: Quoted per call
- Billed: Per record
- Free to start: $0.10
- Endpoint: POST /v1/contacts

## What people build with the Work Email and Phone API

- **Sales outreach.** Reach the people who list their role publicly on LinkedIn: find the profile, then get the work email to write to.
- **Recruiting.** Contact a shortlist of candidates directly, by email or phone, from the profiles you already found.
- **Fix a wrong value.** If a number or email turns out to be wrong, ask again with tryAnotherSource and that part is bought from a different source.

## Quote it, then run it

1. free quote: the exact price, nothing charged:

```bash
curl -X POST https://apiforagents.dev/v1/contacts \
  -H "Authorization: Bearer $AFA_KEY" \
  -H "Content-Type: application/json" \
  -d '{"op":"reveal","subjects":["satyanadella"],"reveal":["email"],"estimateOnly":true}'
```

2. the same call, run:

```bash
curl -X POST https://apiforagents.dev/v1/contacts \
  -H "Authorization: Bearer $AFA_KEY" \
  -H "Content-Type: application/json" \
  -d '{"op":"reveal","subjects":["satyanadella"],"reveal":["email"]}'
```

## Inputs

Everything you can send in one reveal call. Required inputs first.

| Input | Type | What it does |
|---|---|---|
| subjects * | text list | /in/<slug> handles or profile URLs. 1-10 items |
| reveal | enum list | Which parts to reveal. Both by default. A contact is an email AND a number; a phone is five emails' worth, so ask ["email"] when unneeded. |
| verify | boolean | Verify each email found before it counts: an address a verifier calls invalid is kept as a fact but does not satisfy the ask, and the next source is tried. A verdict costs a fraction of a cent per address. |
| tryAnotherSource | boolean | "What I hold is wrong. Get me another." EVERY part in reveal that your org holds is marked wrong and bought again from a source other than the one that gave it, at that part's price. So list only the part that is wrong. One call is one step: the next source's answer is returned even when it is the same value (flagged); ask again to go one source further. Marking is free and final. A part you do not hold is simply revealed. |

## What comes back

The fields of every row, always present. Nothing is guessed: a value that could not be measured is null, and the answer's coverage says why.

| Field | Type |
|---|---|
| publicId | string |
| profileUrl | string |
| name | string |
| title | string |
| company | string |
| emails | list of object |
| phones | list of object |
| firstName | string |
| lastName | string |
| headline | string |
| location | object |
| currentCompany | object |
| experience | list of object |
| education | list of object |
| skills | list of string |
| languages | list of object |
| linkedinUrl | string |
| details | object |

details is always the last field: everything else the source sent for that row, under our own field names. Its keys depend on the source that answered, so read them defensively; it is {} when there is nothing more.

## A sample answer

Made-up names and values in the real field names, so you can see the shape before you spend anything.

| publicId | profileUrl | emails | phones | details |
|---|---|---|---|---|
| ananya-rao | https://www.linkedin.com/in/ananya-rao | [{"value":"ananya.rao@paylane.example","type":"work","status | [{"value":"+91 98450 00000","type":"mobile"}] | {} |
| marcus-lee | https://www.linkedin.com/in/marcus-lee | [{"value":"marcus@northfold.example","type":"work","status": | [{"value":"+44 7700 900123","type":"mobile"}] | {} |
| sofia-ortiz | https://www.linkedin.com/in/sofia-ortiz | [{"value":"sofia.ortiz@kitebank.example","type":"work","stat | [] | {} |

## Pricing

Pay as you go, in US dollars, per record. No subscription, nothing expires, $5 first top-up, and every new agent starts with $0.10 free.

| Request | Records | At the list price |
|---|---|---|
| Any request |  | quoted free before the call |

These are per-record list prices. Some calls also carry a minimum, such as a page of search results, so a small request can cost more than the table shows. The quote ("estimateOnly": true) is free, gives the most your exact request can cost, and the charge then settles to what came back. Records that do not come back are refunded.

## Try it without writing code

- [Open the Work Email and Phone API in the playground](https://apiforagents.dev/dashboard/run?platform=contacts&op=reveal): The playground runs any endpoint by hand: pick a platform and what you want from it, fill a short form named in plain words (or press Use sample input), see the free quote on the Run button, run it, then read the answer as a table or JSON and download it as CSV or JSON. The same call is written out as cURL, Python and Node while you type.

## Why this one, and not a scraper you run yourself

- No login, no Contacts account, no cookies, no proxies, no browser to babysit.
- When the site changes its pages, your request stays the same: keeping the reads working is our job, not yours.
- A fetch that fails costs nothing: it is named in the answer with a reason, and the quote says the most a call can cost before it runs.

## Use it from your tools

- [Contacts in n8n](https://apiforagents.dev/integrations/n8n/contacts)
- [Contacts in Make](https://apiforagents.dev/integrations/make/contacts)
- [Contacts in Zapier](https://apiforagents.dev/integrations/zapier/contacts)
- [Contacts in Python](https://apiforagents.dev/integrations/python/contacts)
- [Contacts in LangChain](https://apiforagents.dev/integrations/langchain/contacts)
- [Contacts in Claude Code](https://apiforagents.dev/integrations/claude-code/contacts)

## Questions

### What does the Work Email and Phone API return?

One row per person: the LinkedIn handle and profile URL, the email with its type and, when you ask for checks, its status (valid, invalid, risky or unverified), and the phone with its type. Every answer also carries a trail: the sources tried, in order, with what each found, labelled by number rather than by name.

### What do I pass in?

Up to ten LinkedIn /in/ handles or profile URLs. reveal picks the parts, ["email", "phone"] by default; ask for ["email"] alone when you do not need the number, since a phone is priced at about five emails. Add verify: true to check each email, and tryAnotherSource: true to replace a part you hold that is wrong.

### Where should the LinkedIn handle come from?

From evidence: a search result, a pasted URL or a LinkedIn people search. A handle guessed from a name can belong to someone else and is still charged. LinkedIn member ids (the ones starting ACoAA or ACwAA) are not handles and are refused without charge.

### How much does it cost?

Each part (email or phone) is priced by what it costs to find, and the free quote ("estimateOnly": true) shows the most a call can cost before anything is spent. You pay only when a value is found: a part that comes back empty is not charged, and a part your account already holds is free.

## Why API for Agents

- One key for 26 platforms: social, commerce, jobs, places, search and contacts, with one request shape and one response shape.
- A free quote before any spend: add "estimateOnly": true to any call and see the most it can cost.
- Pay per record in US dollars. No subscription, nothing expires, top-ups from $5.
- $0.10 free to try, no card. An AI agent can sign itself up in one request; a person claims it later.
- Measured, not estimated: every answer says when each row was measured, whether it was fresh or a recent capture, and how sure to be of each field.
- Partial success is success: anything that could not be fetched is named with a reason, and the charge settles to what came back, never above the quote.
- Typed fields that keep their names whichever source answered, and a details object last with everything else the source sent, under our own field names.
- Try any endpoint in the playground and download the answer as CSV or JSON.

## Start

The playground runs any endpoint by hand: pick a platform and what you want from it, fill a short form named in plain words (or press Use sample input), see the free quote on the Run button, run it, then read the answer as a table or JSON and download it as CSV or JSON. The same call is written out as cURL, Python and Node while you type. Open it at https://apiforagents.dev/dashboard/run?platform=contacts&op=reveal (sign in first).

Agents register at https://apiforagents.dev/auth.md (one POST, $0.10 free). People: https://apiforagents.dev/docs#start. Prices: https://apiforagents.dev/pricing.md