Data catalog / posts
Posts data
Full details of a LinkedIn post, including comments and reactions, looked up by URN.
Last updated September 23, 2026
See it in a workflow
Playbooks
Real patterns, recipes, and prompts other builders run on RichAPI
Developer Docs
Auth, request shape, and error handling
FAQ
Frequently asked questions
Full details of a LinkedIn post, including comments and reactions, looked up by URN.
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.