Data catalog / activity
Activity data
Recent activity feeds for a LinkedIn profile — posts, comments, and reactions — via the profile activities endpoint.
In short: RichAPI POST /profile_activities returns a LinkedIn member's recent posts, comments and reactions. Input is the profile's entity URN, with an optional type filter (POST, COMMENT or REACTION), a page size (limit) and a pagination_token. Billing is 2 credits per item returned; a profile with no recent activity returns no items. Authentication is an x-api-key header against https://api.richapi.ai/api/v1. New accounts get 100 free credits and no card.
Last updated October 13, 2026
What a person posted, commented on and reacted to
POST /profile_activities takes a LinkedIn profile and returns that person's recent activity: the posts they wrote, the comments they left, and the posts they reacted to. Set type to POST, COMMENT or REACTION to get one kind, or leave it out to get all three.
The input is the profile's entity URN, the ACoAA… identifier LinkedIn uses for a member, not the public linkedin.com/in/… URL. Results come back a page at a time. Pass the pagination_token from one response to get the next page.
What activity data costs
2 credits per item returned. The bill depends on how active the person is and how many items you ask for, so limit and type are your cost controls.
Checking 200 prospects for their last five posts costs at most 200 × 5 × 2 = 2,000 credits. There is no per-call base charge, so a prospect who has not posted returns no items and costs no credits. Ask for type: "POST" with a small limit when the question is "has this person said anything about X lately", and pull comments and reactions only for the people who pass.
Rate
| Endpoint | What it does | Credits | Billed |
|---|---|---|---|
/profile_activities |
Get a profile's recent posts, comments and reactions for engagement analysis. | 2 | 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.
Where activity fits in a prospecting job
Activity is a filter you run before outreach. A list built from titles and company size tells you who could buy. Activity tells you who is talking about the problem right now.
- Signal-based prospecting starts from something a company or person did this month and turns it into an account list.
- A weekly signal digest runs a saved prompt over job posts, ads and company posts for your target accounts.
- To read one post in full, with its comments and reactions, use the endpoints on posts data.
- To turn an active person into a full record and a work email, follow with person enrichment and the email finder.
Inputs and freshness
- The endpoint needs the URN. If all you have is a profile URL, enrich it first with person enrichment.
- Activity is read when you call, so two calls a week apart can return different items. Store what you pulled if you need to compare over time.
- The same endpoint is a tool on the hosted MCP server, on the same key and credit pool, so an agent can run the check for you. See the MCP server.
Reference
| Name | Type | Required | Description |
|---|---|---|---|
urn | string | Yes | LinkedIn entity URN of the profile |
limit | integer | No | Number of items per page |
pagination_token | string | No | Token from previous response for next page |
type | string | No | Activity type filter: POST, COMMENT, or REACTION (default: all) |
urnstring · Required- LinkedIn entity URN of the profile
limitinteger · Optional- Number of items per page
pagination_tokenstring · Optional- Token from previous response for next page
typestring · Optional- Activity type filter: POST, COMMENT, or REACTION (default: all)
Request
Minimum required parameters for a activity data call.
{
"urn": "ACoAACcJ11oB9WoP2-S-clw3Q64H9_WmNjCJbbk",
"type": "POST",
"limit": 5
}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
