Data catalog / posts

Posts data

Read LinkedIn posts and the people who engage with them: search posts by keyword, list a company's recent posts, open one post with its comments and reactions, and page through everyone who commented or reacted.

In short: RichAPI has four LinkedIn post endpoints. POST /post_details takes an activity URN (urn:li:activity:…) and returns the post's text, media, comments and reaction counts for 1 credit. POST /post_activities pages through a post's comments or reactions (type COMMENT or REACTION, zero-based page, limit) for 3 credits per call. POST /linkedin_company_posts lists a company's recent posts by company URL, numeric ID or universal name, with posted_limit (24h, week, month), at 0.2 credits per post. POST /post_keyword_search searches posts by keyword with date, content type, author and company filters, at 0.1 credits per post.

Last updated October 13, 2026

Four ways into LinkedIn posts

  • POST /post_keyword_search finds posts by keyword. Narrow with datePosted (PAST_24_HOURS, PAST_WEEK, PAST_MONTH), contentType, the author's job titles (authorKeyword) or industry (authorIndustry), or posts from specific companies and people. Sort by RELEVANCE or DATE_POSTED. Up to 50 posts per page.
  • POST /linkedin_company_posts lists what a company posted. Identify the company by linkedin_company_url, numeric linkedin_company_id (the fastest lookup) or linkedin_company_universal_name (the last part of its LinkedIn URL). posted_limit keeps it to the last 24h, week or month.
  • POST /post_details opens one post by its activity URN, urn:li:activity:…, and returns the text, media, reaction counts and, unless you turn them off, the comments and reactions.
  • POST /post_activities pages through the people who commented on a post or reacted to it, type COMMENT or REACTION.

Endpoints and rates

Endpoint What it does Credits Billed
/post_details Get full post details including text, media, comments and reaction counts. 1 per call
/post_activities Get likes, comments and reactions on a specific LinkedIn post. 3 per call
/linkedin_company_posts Get recent posts published by a LinkedIn company. 0.2 per result
/post_keyword_search Search LinkedIn posts by keyword to discover trending content and engagement opportunities. 0.1 per result

Rates are read from the live OpenAPI spec. Credits are prepaid and never expire, and the price of a credit depends on your package: see pricing.

What post data costs

Search and company posts bill per post returned. 50 posts from a keyword search cost 5 credits, and 50 company posts cost 10. Opening a post costs 1 credit. A page of commenters or reactors costs 3 credits whatever its size, so a larger limit gets you more people per credit.

Turn off comments or reactions on post_details when you only need the post. The rate is the same, but the response is smaller.

From a post to a list of people

The people who comment on a competitor's post, or on a post about the problem you solve, have told you what they care about:

  1. Find the posts with keyword search, or list a competitor's posts from the last month.
  2. Page through each post's commenters with post_activities.
  3. Enrich the people you keep with person enrichment, then find their emails with the email finder.

Signal-based prospecting starts from posts, job ads and ads in the same way. To see what one person posts, comments on and reacts to across LinkedIn, use activity data instead.

Paging and URNs

  • Pages count from 0 on post_activities and post_keyword_search, and from 1 on linkedin_company_posts.
  • post_details and post_activities need the activity URN. Keyword search and company posts return a urn for each post, so you rarely build one by hand.
  • posted_limit filters the posts LinkedIn returns. scrape_posted_limit instead keeps reading back in time until it reaches a post older than the threshold, from 1h up to year.

Reference

urnstring · Required
LinkedIn activity URN, e.g. urn:li:activity:7458532524865232896.
commentsboolean · Optional
Include comments list in response. Defaults to true.
reactionsboolean · Optional
Include reactions list in response. Defaults to true.

Request

Minimum required parameters for a posts data call.

Request
{
  "urn": "urn:li:activity:7458532524865232896",
  "comments": true,
  "reactions": false
}

See it in a workflow

Playbooks

Real patterns, recipes, and prompts other builders run on RichAPI

Start free with 100 credits

Developer Docs

Auth, request shape, and error handling

See Documentation

FAQ

Frequently asked questions

Read LinkedIn posts and the people who engage with them: search posts by keyword, list a company's recent posts, open one post with its comments and reactions, and page through everyone who commented or reacted.
Every endpoint is billed from the same credit pool, at the published rate on /pricing — never a separate contract per endpoint.
Yes — the same endpoint is reachable from an MCP client (Claude, ChatGPT, Cursor, Windsurf) using the same key and credit pool. See /mcp.

Related data

Proxycurl Company Profile Endpoint replacementProxycurl's Company Profile Endpoint took a LinkedIn company page URL and returned a company record. POST /enrich_company takes the same input. If your pipeline was passing a domain instead, read the section on that before you plan the work, because we cannot do domain-in company enrichment on a public endpoint today and that is the expensive part of this migration.Proxycurl Employee Listing replacementProxycurl's Employee Listing returned the people at a company. POST /linkedin_company_employees_search takes a LinkedIn company URL and a page number and returns an elements array. Billing here is per result rather than per call, which changes how you write the pagination loop and how you budget a large org.Proxycurl Person Lookup (email) replacementProxycurl resolved an email address to a person in one request. RichAPI does it in two: POST /find_linkedin_url_by_email returns the profile URL, then POST /enrich_profile turns that into the record. Two calls, two charges, and both of them bill on a 2xx even when the answer is empty. Price the chain, not the call.Proxycurl Person Profile Endpoint replacementProxycurl's Person Profile Endpoint took a LinkedIn profile URL and returned a person record. POST /enrich_profile takes the same input and returns the same kind of record under different field names. The URL swap is ten minutes; re-mapping the fields is the afternoon. This page covers both, and is clear that a 2xx bills even when the record comes back thin.