Data catalog / activity

Activity data

Recent activity feeds for a LinkedIn profile — posts, comments, and reactions — via the profile activities endpoint.

Last updated September 23, 2026

How it works

Pass a LinkedIn profile URN and this endpoint returns that person's recent posts, comments, and reactions. It's the same signal that powers signal-based prospecting: instead of guessing who's active, you pull a feed of people who demonstrably are.

When to use it

Run it on a list of prospects to see who's recently posted about a relevant topic, before you reach out — a quick, cheap qualifier that beats cold-emailing a static list. Pair it with enrich_profile and email_finder to go from "this person is active" to "here's their verified email" in one pipeline.

Reference

urnstring · Required
LinkedIn profile entity URN.
typestring · Optional
POST, COMMENT, or REACTION. Defaults to POST.
sizeinteger · Optional
Items per page. Defaults to 10.
paginationTokenstring · Optional
Token from a previous response, for the next page.
useCacheboolean · Optional
Use cached data (up to 24h). Defaults to true.

Request

Minimum required parameters for a activity data call.

Request
{
  "urn": "ACoAACcJ11oB9WoP2-S-clw3Q64H9_WmNjCJbbk",
  "type": "POST",
  "size": 10
}

See it in a workflow

Playbooks

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

Start free with 25 credits

Developer Docs

Auth, request shape, and error handling

See Documentation

FAQ

Frequently asked questions

Recent activity feeds for a LinkedIn profile — posts, comments, and reactions — via the profile activities endpoint.
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