Professional Network Data, endpoint reference, Up

34 of 34

Quirks worth learning before your first call

Pagination. Almost every list endpoint accepts start as a numeric offset (0, 10, 20, ...). There is no opaque pagination token. When in doubt, increment start by the page size returned in the previous batch.

Date filtering on posts. get-profile-posts takes postedAt=YYYY-MM-DD and returns only posts newer than that date. For an outbound research workflow, pass today minus 7 so you only spend a credit when the prospect actually posted recently.

Username vs URL. Most profile endpoints accept either username (the slug after linkedin.com/in/, case-sensitive) or, on a different path, the full url. The slug version is a hair faster; the URL version forgives copy-paste.

Free errors. When the response body contains "You will not be charged for this request", no credit was deducted, even though HTTP was 200. Anything else (success or empty array) costs one credit.

The lone POST. Only search-people-by-url uses POST with a JSON body. Everything else is GET with query parameters.

Profile enrichment

15 endpoints

Person-level reads. Turn a LinkedIn slug or URL into structured profile data, recent activity, and social proof for personalization.

GET / Profile by username #1

Use whenYou have the LinkedIn slug (e.g. adamselipsky from linkedin.com/in/adamselipsky/) and need core profile fields: name, headline, current role, education, location.

Param	Type	Required	Notes
username	string	yes	Case-sensitive. Take the exact slug from the URL.

# Profile by username (root path of the API)
curl -G 'https://professional-network-data.p.rapidapi.com/' \
  --data-urlencode 'username=adamselipsky' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

NuanceThe path is literally /, not /profile or /get-profile. Easy to miss.

GET /get-profile-data-by-url Profile by URL #2

Use whenYou have the full LinkedIn URL pasted from a CSV and don't want to parse the slug yourself.

Param	Type	Required	Notes
url	string (URL)	yes	Full `https://www.linkedin.com/in/...` URL. Trailing slash optional.

curl -G 'https://professional-network-data.p.rapidapi.com/get-profile-data-by-url' \
  --data-urlencode 'url=https://www.linkedin.com/in/adamselipsky/' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

NuanceSame payload as /. Pick this one in workflows where the input column is linkedin_url and slug parsing is fragile.

GET /all-profile-data Full profile dump #3

Use whenYou want everything: positions, education, certifications, projects, skills, languages, accomplishments, in one shot.

Param	Type	Required	Notes
username	string	yes	LinkedIn slug.

curl -G 'https://professional-network-data.p.rapidapi.com/all-profile-data' \
  --data-urlencode 'username=adamselipsky' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

NuanceHeaviest payload of the profile family. If you only need headline + role, use #1 instead; the response body is roughly 5x smaller.

GET /connection-count Connections and followers #4

Use whenLightweight signal pull. Just the connection count and follower count, perfect for "is this person a public figure" gating.

Param	Type	Required	Notes
username	string	yes	LinkedIn slug.

curl -G 'https://professional-network-data.p.rapidapi.com/connection-count' \
  --data-urlencode 'username=adamselipsky' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

GET /data-connection-count Profile plus connection count #5

Use whenYou want the standard profile fields and the connection count in one credit instead of two.

Param	Type	Required	Notes
username	string	yes	LinkedIn slug.

curl -G 'https://professional-network-data.p.rapidapi.com/data-connection-count' \
  --data-urlencode 'username=adamselipsky' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

NuanceOne of three combo endpoints (#5, #6) that bundle reads to save credits. Use these instead of chaining two separate calls in Clay.

GET /profile-data-connection-count-posts Profile, connections and recent posts #6

Use whenEmail personalization workflows. One call gives you the role for context, the connection count for credibility, and the recent posts for the personalization hook.

Param	Type	Required	Notes
username	string	yes	LinkedIn slug.

curl -G 'https://professional-network-data.p.rapidapi.com/profile-data-connection-count-posts' \
  --data-urlencode 'username=adamselipsky' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

NuanceBest ROI per credit for prospect research. Replaces three separate calls (#1 + #4 + #8).

GET /similar-profiles People also viewed #7

Use whenYou found one good prospect and want LinkedIn's own list of look-alikes for list expansion.

Param	Type	Required	Notes
url	string (URL)	yes	Full LinkedIn profile URL, not the slug.

curl -G 'https://professional-network-data.p.rapidapi.com/similar-profiles' \
  --data-urlencode 'url=https://www.linkedin.com/in/adamselipsky/' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

NuanceOutlier in the family: requires the URL form, not the username. Will reject ?username=.

GET /get-profile-posts Profile post feed, date-filtered #8

Use whenYou want the prospect's recent posts as a personalization hook. Pair with get-profile-recent-activity-time to skip dormant accounts before spending a credit on the feed.

Param	Type	Required	Notes
username	string	yes	LinkedIn slug.
postedAt	date YYYY-MM-DD	no	Returns only posts newer than this date. Default in workflows: `today() - 7`.
start	int	no	Pagination offset, defaults to 0.

curl -G 'https://professional-network-data.p.rapidapi.com/get-profile-posts' \
  --data-urlencode 'username=adamselipsky' \
  --data-urlencode 'postedAt=2026-04-18' \
  --data-urlencode 'start=0' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

NuancepostedAt behaves as a "newer than" filter, not "exact date". To paginate, hold postedAt constant and bump start by the batch size.

GET /get-profile-comments Comments the user left elsewhere #9

Use whenYou want the conversations a prospect engages with, not what they post themselves. Stronger signal than posts in some industries (their reactions to other VCs, founders, etc.).

Param	Type	Required	Notes
username	string	yes	LinkedIn slug.
start	int	no	Pagination offset.

curl -G 'https://professional-network-data.p.rapidapi.com/get-profile-comments' \
  --data-urlencode 'username=adamselipsky' \
  --data-urlencode 'start=0' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

GET /get-profile-likes Posts the user reacted to #10

Use whenYou need a passive engagement signal. Likes are a softer indicator than comments but cover a wider surface, useful for tracking what topics a prospect actually consumes.

Param	Type	Required	Notes
username	string	yes	LinkedIn slug.
start	int	no	Pagination offset.

curl -G 'https://professional-network-data.p.rapidapi.com/get-profile-likes' \
  --data-urlencode 'username=adamselipsky' \
  --data-urlencode 'start=0' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

GET /get-profile-posts-comments Posts and comments interleaved #11

Use whenYou want a single chronological activity feed mixing what the prospect posted and what they commented on. One credit, both signals.

Param	Type	Required	Notes
username	string	yes	LinkedIn slug.
start	int	no	Pagination offset.

curl -G 'https://professional-network-data.p.rapidapi.com/get-profile-posts-comments' \
  --data-urlencode 'username=adamselipsky' \
  --data-urlencode 'start=0' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

NuanceDifferent from #12 (single post + its comment thread). This one is a feed of all the user's posts and comments together.

GET /get-profile-post-and-comments One post with its comment thread #12

Use whenYou picked a specific post URL and want the full comment thread under it (both who said what and how long ago).

Param	Type	Required	Notes
url	string (URL)	yes	Full LinkedIn post URL, including the activity ID.

curl -G 'https://professional-network-data.p.rapidapi.com/get-profile-post-and-comments' \
  --data-urlencode 'url=https://www.linkedin.com/posts/adamselipsky_activity-7301129026870468608' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

GET /get-profile-recent-activity-time Last activity timestamp #13

Use whenCheap pre-flight check. Hit this first to skip dormant prospects before paying for the full post feed.

Param	Type	Required	Notes
username	string	yes	LinkedIn slug.

curl -G 'https://professional-network-data.p.rapidapi.com/get-profile-recent-activity-time' \
  --data-urlencode 'username=adamselipsky' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

NuanceSequence: call this, branch on freshness (e.g. last 30 days), only then call get-profile-posts. Saves a meaningful chunk of credits on cold lists.

GET /get-given-recommendations Recommendations the user wrote #14

Use whenYou want to map a prospect's network of trust outward: who they have publicly endorsed (often coworkers, ex-reports, founders they backed).

Param	Type	Required	Notes
username	string	yes	LinkedIn slug.

curl -G 'https://professional-network-data.p.rapidapi.com/get-given-recommendations' \
  --data-urlencode 'username=adamselipsky' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

GET /get-received-recommendations Recommendations written about the user #15

Use whenYou want third-party social proof, ready-made quotes describing the prospect's strengths, often useful for "warm angle" hooks in cold copy.

Param	Type	Required	Notes
username	string	yes	LinkedIn slug.

curl -G 'https://professional-network-data.p.rapidapi.com/get-received-recommendations' \
  --data-urlencode 'username=adamselipsky' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

Articles

4 endpoints

Long-form LinkedIn content. Identified by the /pulse/ URL pattern, not /posts/.

GET/get-articleArticle body#16

Use whenYou need the full article text for a thought-leadership reference or to ground an AI summary.

Param	Type	Required	Notes
url	string (URL)	yes	Full `linkedin.com/pulse/...` URL.

curl -G 'https://professional-network-data.p.rapidapi.com/get-article' \
  --data-urlencode 'url=https://www.linkedin.com/pulse/your-article-slug' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

GET/get-article-commentsArticle comment thread#17

Use whenYou want to surface who is engaging with a piece of content (great for finding warm leads commenting on a competitor's article).

Param	Type	Required	Notes
url	string (URL)	yes	Article URL.

curl -G 'https://professional-network-data.p.rapidapi.com/get-article-comments' \
  --data-urlencode 'url=https://www.linkedin.com/pulse/your-article-slug' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

GET/get-article-reactionsArticle reactions, who liked it#18

Use whenYou want the list of profiles who reacted to an article (lighter signal than commenters but a much wider net).

Param	Type	Required	Notes
url	string (URL)	yes	Article URL.

curl -G 'https://professional-network-data.p.rapidapi.com/get-article-reactions' \
  --data-urlencode 'url=https://www.linkedin.com/pulse/your-article-slug' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

GET/get-user-articlesAll articles by a user#19

Use whenYou want to inventory a thought-leader's published catalog before reaching out, for instance to reference a specific article in cold copy.

Param	Type	Required	Notes
username	string	yes	LinkedIn slug, or pass a profile URL via the `url` param (either works).

curl -G 'https://professional-network-data.p.rapidapi.com/get-user-articles' \
  --data-urlencode 'username=adamselipsky' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

NuanceAccepts either username or url (the API's error message says "username or profile URL"). Pick whichever your input data has.

Posts

1 endpoint

Single-post lookup. For an entire post feed, see profile post feed (#8) or company post feed (#28).

GET/get-postSingle post details#20

Use whenYou have a specific post URL and need its body, author, reaction count, and metadata.

Param	Type	Required	Notes
url	string (URL)	yes	Full `linkedin.com/posts/...` URL.

curl -G 'https://professional-network-data.p.rapidapi.com/get-post' \
  --data-urlencode 'url=https://www.linkedin.com/posts/adamselipsky_activity-7301129026870468608' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

Company enrichment

10 endpoints

Account-level reads. The three identifier flavors are domain (most common in CRM data), LinkedIn slug, and numeric ID. Pick the one matching your input column.

GET/get-company-by-domainResolve company from a website domain#21

Use whenThis is the workhorse for B2B enrichment. CSV has company_domain, you want headcount, industry, LinkedIn URL, HQ location.

Param	Type	Required	Notes
domain	string	yes	Bare domain (e.g. `anthropic.com`). Strip `https://` and `www.`.

curl -G 'https://professional-network-data.p.rapidapi.com/get-company-by-domain' \
  --data-urlencode 'domain=anthropic.com' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

GET/get-company-detailsResolve company from a LinkedIn slug#22

Use whenYour input is the LinkedIn company URL slug (e.g. anthropicresearch from linkedin.com/company/anthropicresearch/).

Param	Type	Required	Notes
username	string	yes	Company slug (the API calls this "company username").

curl -G 'https://professional-network-data.p.rapidapi.com/get-company-details' \
  --data-urlencode 'username=anthropicresearch' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

GET/get-company-details-by-idResolve company from a numeric ID#23

Use whenYou have stored LinkedIn's internal numeric company ID (e.g. from a previous response).

Param	Type	Required	Notes
id	int	yes	LinkedIn company ID.

curl -G 'https://professional-network-data.p.rapidapi.com/get-company-details-by-id' \
  --data-urlencode 'id=10186' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

NuanceThe numeric ID is stable across slug renames, useful when LinkedIn rebrands a company page.

GET/get-company-insightsHeadcount trends and growth signals#24

Use whenYou want to detect "growing fast" or "shrinking" signals on a target account: headcount over time, function distribution, growth percentage.

Param	Type	Required	Notes
username	string	yes	Company slug.

curl -G 'https://professional-network-data.p.rapidapi.com/get-company-insights' \
  --data-urlencode 'username=anthropicresearch' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

GET/get-company-jobs-countOpen headcount as a hiring signal#25

Use whenQuick, single-number signal for ICP scoring. "Are they hiring at all?" Often a more honest growth indicator than press releases.

Param	Type	Required	Notes
username	string	no	Company slug. If omitted, returns the global LinkedIn jobs total.

curl -G 'https://professional-network-data.p.rapidapi.com/get-company-jobs-count' \
  --data-urlencode 'username=anthropicresearch' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

NuanceReturns {"total": N}. Calling without username returns the LinkedIn-wide job count (~8M), useful as a quick credit-check but not for prospecting.

GET/get-company-pages-people-also-viewedCompany look-alikes#26

Use whenList expansion at the account level. You have one ICP-fit account, you want LinkedIn's own list of similar companies (often competitors or peers).

Param	Type	Required	Notes
username	string	yes	Company slug.

curl -G 'https://professional-network-data.p.rapidapi.com/get-company-pages-people-also-viewed' \
  --data-urlencode 'username=anthropicresearch' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

GET/get-company-post-commentsComments on a company post#27

Use whenYou spotted a high-engagement company post (product launch, hiring announcement) and want the people commenting as warm prospects.

Param	Type	Required	Notes
url	string (URL)	yes	Full company post URL.

curl -G 'https://professional-network-data.p.rapidapi.com/get-company-post-comments' \
  --data-urlencode 'url=https://www.linkedin.com/posts/anthropicresearch_activity-XXXX' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

GET/get-company-postsRecent posts from a company page#28

Use whenYou want to monitor what an account is saying publicly: launches, milestones, hiring pushes. Pair with a scheduler to detect intent shifts.

Param	Type	Required	Notes
username	string	yes	Company slug.
start	int	no	Pagination offset.

curl -G 'https://professional-network-data.p.rapidapi.com/get-company-posts' \
  --data-urlencode 'username=anthropicresearch' \
  --data-urlencode 'start=0' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

GET/get-hiring-teamRecruiters listed on a job#29

Use whenYou want to reach the hiring manager or recruiter behind a specific job posting (great for staffing or recruitment-tech outreach).

Param	Type	Required	Notes
jobId	int	one of	LinkedIn job ID.
jobUrl	string (URL)	one of	Full job URL, alternative to `jobId`.

curl -G 'https://professional-network-data.p.rapidapi.com/get-hiring-team' \
  --data-urlencode 'jobUrl=https://www.linkedin.com/jobs/view/4406638259' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

NuanceThe error message reads "Job id or job url is required", confirming either is accepted. Use whichever your CSV has.

GET/get-job-detailsFull job posting#30

Use whenJob-data prospecting. Returns full description, seniority, location, salary range (when posted), and the parent company.

Param	Type	Required	Notes
jobId	int	yes	LinkedIn job ID.

curl -G 'https://professional-network-data.p.rapidapi.com/get-job-details' \
  --data-urlencode 'jobId=4406638259' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

Search

4 endpoints

Discovery layer for building lists from scratch. People, jobs, locations, plus the only POST endpoint of the API for replaying a LinkedIn search URL.

GET/search-peopleBuild a people list from keywords#31

Use whenYou're building a fresh list and only have role keywords or names. Returns a paginated array with fullName, headline, profileUrl, and total count.

Param	Type	Required	Notes
keywords	string	no	Free text. URL-encode spaces.
start	int	no	Pagination offset (typically +10 per page).

curl -G 'https://professional-network-data.p.rapidapi.com/search-people' \
  --data-urlencode 'keywords=growth marketing director' \
  --data-urlencode 'start=0' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

NuanceVerified live: returns {"total":1.27B,"items":[...]} with no params at all. The total is the full LinkedIn population matching, not what you'll get back. Use it as a sanity check on filter tightness, then paginate with start.

POST/search-people-by-urlReplay a LinkedIn search URL#32

Use whenYou constructed a complex search in LinkedIn's UI (with multi-filter combinations) and want to scrape the result set programmatically. Just paste the URL.

Param	Type	Required	Notes
url	string (URL), JSON body	yes	The full `linkedin.com/search/results/people/?...` URL.

curl -X POST 'https://professional-network-data.p.rapidapi.com/search-people-by-url' \
  -H 'Content-Type: application/json' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere' \
  -d '{"url":"https://www.linkedin.com/search/results/people/?keywords=growth%20marketing"}'

NuanceThe only POST endpoint in the API. The body field is url, not linkedinUrl or searchUrl. JSON content type required.

GET/search-jobsSearch the LinkedIn job board#33

Use whenJob-data prospecting at the discovery stage. Returns id, title, URL, company, logo, posted date, location.

Param	Type	Required	Notes
keywords	string	no	Role keywords.
location	string	no	Plain-text location, e.g. `United States`.
start	int	no	Pagination offset.

curl -G 'https://professional-network-data.p.rapidapi.com/search-jobs' \
  --data-urlencode 'keywords=ai engineer' \
  --data-urlencode 'location=United States' \
  --data-urlencode 'start=0' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

NuanceVerified working with no params at all (returns a default feed). For tight ICP filters, combine keywords with a location resolved via endpoint #34.

GET/search-locationsResolve a place name to LinkedIn's geo IDs#34

Use whenPre-step before search-people or search-jobs: turn "Bangalore" into the canonical LinkedIn geoUrn for accurate filtering.

Param	Type	Required	Notes
keyword	string	yes	Singular `keyword` (note: not `keywords` like the other search endpoints).

curl -G 'https://professional-network-data.p.rapidapi.com/search-locations' \
  --data-urlencode 'keyword=Bangalore' \
  -H 'x-rapidapi-host: professional-network-data.p.rapidapi.com' \
  -H 'x-rapidapi-key: yourapikeygoeshere'

NuanceThe param is keyword (singular). Every other search endpoint uses keywords (plural). Easy mistake.

Listed in the sidebar, returning 404

These appear in the RapidAPI marketplace UI for this API. The live host returns 404 endpoint does not exist for every variant tested (with and without the get- prefix, with and without trailing s, etc.). Treat them as deprecated. If you need any of them, write to professional.network.data@gmail.com; the provider explicitly notes RapidAPI messages are unmonitored.

/get-post-reactions
/get-post-reposts
/get-company-employees-count
/affiliated-pages, /get-affiliated-pages
/groups, /get-profile-groups
/schools, /get-profile-schools
/newsletters, /get-profile-newsletters
/position-skills, /get-profile-position-skills
/top-voices, /get-profile-top-voices
/get-profile-company-interests
/get-profile-top-position
/search-companies (any variant)
/search-posts
/search-posts-by-hashtag
/search-jobs-v
/posted-jobs, /get-posted-jobs

Every live endpoint of Professional Network Data, with the curls that actually work.