List LinkedIn User Posts

View all LinkedIn Data API endpoints →

Use the profile urn with optional page and pagination_cursor. The documented data array contains id, text, created_at, url, share_urn, author, content and activity; the response also has page and pagination_token. Supply a returned pagination_token through the public pagination_cursor field for continuation. This sample does not expose the same has_more/total contract as company posts, so do not assume uniform pagination across feeds.

API Features

Profile-publishing scope A profile urn identifies the person whose available posts are requested.
Post text and source identity id, share_urn and url support source-linked records of the returned publishing activity.
Feed continuation cursor Pass returned pagination_token as pagination_cursor without treating it as a login credential.
Author-feed media and activity content and activity carry available attachments and engagement fields for each returned post.

Live API Demo

GET /api/project/linkedin-scraper/get-user-posts

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/linkedin-scraper/get-user-posts?key=<API_KEY>&urn=<urn>&page=1'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

Is pagination the same as company posts?

No. The documented user-post response includes page and pagination_token rather than establishing a has_more/total contract. Send the returned token as pagination_cursor and do not invent continuation values.

Does the feed guarantee a complete publishing history?

No. Availability and continuation depend on the returned data. Keep source links and collection dates, and do not claim complete or permanent coverage.

Related operations

Guides

View Subscription Plans →