Skip to main content
GET
Get posts a profile has reacted to

Endpoint

Authentication

Include your API key in the request header:

Parameters

string
required
The professional profile whose reactions to fetch. Accepts any of:
  • Profile URN, recommended for consistency: a profile’s public identifier (slug) can change over time, the URN does not. Example: urn:li:fsd_profile:ACoAAA8BYqEBCGLg_vT_ca6mMEqkpp9nVffJ3hc
  • Public identifier (slug), also fine. Example: williamhgates
  • Profile URL. Example: https://www.linkedin.com/in/williamhgates (a trailing slash makes no difference)
The slug is the last path segment of a profile URL (linkedin.com/in/<slug>). Pass just the slug, not the /in/ prefix.
integer
default:"10"
Number of reactions to fetch per page.
  • Minimum: 1
  • Maximum: 50
  • Default: 10
integer
default:"0"
deprecated
Not supported on this endpoint. This feed is cursor-paginated and ignores offsets, so a non-zero start is rejected with 400 rather than silently returning the first page again. Use paginationToken.
string
Cursor for the next page. Pass back the paginationToken from the previous response, unchanged; omit it to start from the beginning. A value this API did not issue is rejected with 400. Keep paging while hasMore is true.

Response

array
Array of reactions, each containing the reaction type and the post that was reacted to
string
Token for fetching the next page of reactions. Only present when more reactions are available.
boolean
Indicates whether there are more reactions to fetch.

Example Request

Example Response

Errors

See Error Handling for the full list of error codes and recommended handling.
  • 400 MISSING_PARAMETER / INVALID_URN
  • 401 INVALID_API_KEY
  • 404 PROFILE_NOT_FOUND
  • 402 QUOTA_EXHAUSTED
  • 429 RATE_LIMITED
  • 500 INTERNAL_ERROR
  • 503 SERVICE_UNAVAILABLE

Pagination

To fetch all reactions from a profile, use pagination:
  1. Make an initial request without paginationToken
  2. If hasMore is true, use the returned paginationToken in your next request
  3. Continue until hasMore is false

Reaction Types

Notes

This endpoint consumes 1 credit from your credit balance per API call, regardless of the count parameter value. Errors are free — with one exception: a 404 not found costs 1 credit. See Quotas.
Reactions are returned in reverse chronological order (most recent reactions first). The post object within each reaction has the same shape as items from GET /api/v1/posts, so you can reuse the same types in your client code.
Use the paginationToken to efficiently paginate through a profile’s reaction history without re-fetching already retrieved reactions.

Use Cases

Competitive intelligence

Monitor what content your competitors are engaging with

Interest analysis

Understand a prospect’s interests based on the posts they react to

Content research

Discover trending content in your industry by analyzing reactions of key influencers

Lead scoring

Enrich lead profiles with engagement activity data

Authorizations

X-API-Key
string
header
required

Query Parameters

profileUrlOrUrn
string
required

The professional profile to fetch. Accepts a profile URN (recommended for consistency, since a profile's public identifier can change over time while the URN does not; example urn:li:fsd_profile:ACoAAA8BYqEBCGLg_vT_ca6mMEqkpp9nVffJ3hc), a public identifier/slug (also fine; example williamhgates), or a full profile URL (example https://www.linkedin.com/in/williamhgates; a trailing slash is ignored). The slug is the last path segment of a profile URL, so pass just the slug, not the /in/ prefix.

Example:

"urn:li:fsd_profile:ACoAAA8BYqEBCGLg_vT_ca6mMEqkpp9nVffJ3hc"

count
integer
default:10

Number of reactions to fetch (default: 10)

Required range: 1 <= x <= 50
start
integer
default:0

Not supported on this endpoint. This feed is cursor-paginated and ignores offsets, so a non-zero value is rejected with 400 rather than silently returning the first page again. Page with paginationToken instead.

Required range: x >= 0
paginationToken
string

Cursor for the next page: pass back the paginationToken from the previous response, unchanged. Omit it to start from the beginning. A value this API did not issue is rejected with 400. Keep paging while hasMore is true.

Response

Successfully fetched profile reactions

reactions
object[]
paginationToken
string

Token for fetching the next page

hasMore
boolean

Whether more reactions are available