LinkedIn data API
for profiles, search and posts

The numbers

Per our live price list and the API's own limits, read each time this page renders: 6 reads on sale, one price for all of them.

Price per live read

$0.012

Charged only when the read is served.

Reads for $1

83

A new account starts with $1 free.

Results per search query

1,000

Narrow with filters to read a whole market.

Requests a minute per key

60

Over it: 429 with Retry-After, never billed.

What you can read

6 live reads behind one API key. Prices come from GET /pricing; a route marked launching soon is not on sale yet.

How it works

1. 1

   Create a key

   Sign up, open the dashboard and create an API key. The first $1 is free and needs no card.

2. 2

   Find the people

   Search by keywords and filters, or start from a profile address you already have. Each result carries a person reference for the next call.

3. 3

   Read what they post and who engages

   Read a person's recent posts, then the people who reacted to or commented on any public post, to find warm accounts around a topic or a competitor.

Your first request

Ten people whose profile matches "head of revenue" in the United States.

curl -X POST https://api.prospectapis.com/v1/people/search \
  -H "Authorization: Bearer $PROSPECTAPIS_KEY" \
  -H "Content-Type: application/json" \
  -d '{"keywords": "head of revenue", "filters": {"location": "United States"}, "count": 10}'

The answer has two parts: data, the results with a page to read the next set (1 to 50 a page), and coverage, how many of the expected fields the source carried, so your code can tell a sparse profile from a missing one.

{
  "data": { "items": [ { "person_ref": "...", "name": "...", "headline": "..." } ], "page": { "start": 0, "count": 10 } },
  "coverage": { "filled": 9, "of": 10 }
}

Every parameter, field and error is in the search reference, with the profile, posts and engagers pages beside it.

What teams build with it

• Account research before a call. Read the buyer's profile and last posts minutes before the meeting, so the first question is about what they said this week.
• An agent that researches. Give an agent the reads as tools; our guide to researching prospects with an AI agent shows where they fit.
• A list from a conversation. Read who reacted to or commented on a post about your category or a competitor's launch, and start with the people already paying attention.
• The founder behind a launch. A record from the launch signals API names the person who posted it; read their profile next.
• A market by title and company. Search people by title, current company, location and industry, then split the market with filters to stay under the 1,000-result window.
• Your own page's audience. Read the followers of a company page your connected account administers; connecting is free.

Pricing

$0.012 per live read, from a prepaid balance in US dollars. No plan, no seat and no monthly fee; credits never expire. A new account starts with $1 free and no card, which covers 83 reads. Every product is on the pricing page.

Fresh at request time, free when it fails

• Live, not a stale database. A read fetches the profile or post when you call it, so a job change or a new post shows up the same day.
• Pay per read, no seat. One prepaid balance in US dollars, $0.012 a read, shared with every other ProspectAPIs API, and credits never expire. Unread profiles and removed people are free.
• Engagement as a signal. The people who react to and comment on a post about your category are the warmest list you can build, and the engagers read returns them.
• Made for agents too. Every read is an MCP tool, so an agent can search, read and qualify people on the same key.

Removal and fair use

The reads return only public profile data. A person who asks to be removed is dropped from every people read, matched by both their public profile handle and our internal reference, and a call that names them answers 404 with no charge. Requests go to the address on our privacy policy. To act on your own account instead of reading, see the LinkedIn automation API; to check the email addresses you find, use the email verifier.

LinkedIn is a trademark of its owner. ProspectAPIs is an independent service and is not affiliated with, endorsed by or sponsored by LinkedIn. You are responsible for following its user agreement; see our terms and acceptable use policy.

Questions

What does the LinkedIn data API return?

Public profiles, people search results, a person's recent posts, the people who reacted to or commented on a post and a company page's public fields, as JSON. The followers of a company page are available when your own connected account administers that page.

Is the data live or from a database?

Live. Each call reads the person or post at the moment you ask; it is not served from a stored copy of anyone's profile.

How much does a read cost?

$0.012 per live read, drawn from a prepaid balance. A profile that cannot be read is free, and a person who asked to be removed is answered with 404 and not charged. There is no seat and no monthly fee.

Do I need to connect my own LinkedIn account?

No for profiles, search, posts and engagers. Yes only for the followers of a company page, which LinkedIn shows to that page's administrators.

Are there limits?

Each key makes up to 60 requests a minute. If your account reaches its daily limit on people reads, the call answers 429 with a Retry-After to 00:00 UTC and is not charged. A search reads at most the first 1,000 results of a query, so split a large market with filters.

What about people who do not want to be in the data?

Anyone can ask to be removed through the address on our privacy policy. After that, no people read returns them.

Can an AI agent use it?

Yes. The hosted MCP server and the npm package prospectapis-mcp expose each read as a tool on the same key and balance.

Is ProspectAPIs part of LinkedIn?

No. ProspectAPIs is an independent service and is not affiliated with, endorsed by or sponsored by LinkedIn. LinkedIn is a trademark of its owner.