LinkedIn Profile Posts
A LinkedIn profile-associated feed can contain authored posts, reposts, articles, images, videos, documents, and other public activity from a member page. Returned records provide a collection-time sample for content research, but they do not represent a complete activity history, private analytics, or connection-only visibility.
Features
- Discovery from profile URLsAccept one or more public LinkedIn /in/ URLs and discover posts associated with each submitted profile.
- Optional authored-post filteringForward only_authored_posts to reduce associated activity to posts the provider identifies as authored by the target profile.
- Provider date windowsForward optional start_date and end_date strings for provider-side filtering without imposing a local format, ordering, inclusiveness, or time-zone rule.
- Normalized content contextReturn available post text, author fields, publication time, media, hashtags, mentions, and source URL in a stable post schema.
- Visible engagement snapshotsKeep available likes, comments, shares, and views with collected_at so measurements remain tied to their observation time.
Parameters
| Parameters | Required | Description |
|---|---|---|
urls | Required | Required list of public LinkedIn profile URLs on LinkedIn hosts with paths beginning with /in/. |
start_date | Optional | Optional non-empty provider date-filter string forwarded for every input profile; SocQ does not parse or validate its format or inclusiveness. |
end_date | Optional | Optional non-empty provider date-filter string forwarded for every input profile; SocQ does not order-check it against start_date. |
only_authored_posts | Optional | Optional boolean forwarded for every profile; true requests provider-identified authored posts but is not a SocQ-side identity audit. |
results_limit | Optional | Optional integer from 1 through 2000, applied separately to every profile URL and defaulting to 100 per profile. |
How to Use
Submit profile URLs and discovery controls, follow the asynchronous task, and page through the stored normalized posts.
- Prepare one or more public LinkedIn profile URLs whose paths begin with /in/.
- Choose only_authored_posts and a results_limit from 1 through 2000 for each profile; add provider date strings only when needed.
- POST the request to /v1/linkedin/profile-posts and poll /v1/tasks/{task_id} until it succeeds or fails.
- Read data.results.items and continue with next_cursor while has_more is true.
curl -X POST "https://api.socq.ai/v1/linkedin/profile-posts" \
-H "Authorization: Bearer $SOCQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{"urls":["https://www.linkedin.com/in/satyanadella/"],"only_authored_posts":true,"results_limit":20}'
# Poll GET /v1/tasks/{task_id}
# Read data.results.items and follow next_cursor while has_more is trueBest Use Cases
- Public communication review: Study topics, claims, links, and recurring language across the returned posts associated with selected professional profiles.
- Authored-content sampling: Use only_authored_posts to request a narrower sample, then inspect returned author fields whenever authorship matters.
- Format and media research: Compare available image, video, document, article, hashtag, and mention patterns within a defined set of returned records.
- Time-bounded engagement snapshots: Apply provider date strings and compare visible engagement only within the collected sample, retaining published_at and collected_at.
Pro Tips
- Treat results_limit as a per-profile ceiling: five URLs with a limit of 20 can store up to 100 posts.
- Keep date inputs as provider strings and document your own convention because SocQ does not validate their format, ordering, boundaries, or time zone.
- Verify the returned author when only_authored_posts is important; the flag requests provider filtering rather than proving identity.
- Preserve collected_at beside engagement metrics because visible counts can change between runs.
- Keep null distinct from zero for timestamps and metrics, and allow media, hashtags, or mentions to be empty.
- Do not infer expertise, employment status, sentiment, lead quality, influence, or content effectiveness from the normalized sample alone.
Related APIs
Use these APIs when you need a different type of public LinkedIn data.
- LinkedIn Profiles API — Normalize public profile identity, roles, location, visible audience counts, experience, education, and skills from profile URLs.
- LinkedIn Companies API — Normalize public company descriptions, websites, logos, visible audience and employee counts, industries, locations, and specialties.
- LinkedIn Posts API — Collect public post text, authors, visible engagement, media, publication time, type, and hashtags from supported URLs.
- LinkedIn Jobs API — Normalize public job titles, companies, descriptions, locations, qualifications, employment details, application links, and available salary fields.
- LinkedIn Company Jobs API — Discover public job listings from prepared LinkedIn /jobs/ URLs with normalized role, company, location, employment, experience, remote, salary, and timing fields.
- LinkedIn Company Posts API — Discover public posts from LinkedIn company-page URLs with text, author context, media, hashtags, timestamps, and visible engagement.
- LinkedIn Post Comments API — Collect public comments exposed with a known LinkedIn post, including text, author context, timestamps, relationship IDs, and visible likes and reply counts.
- LinkedIn Search Jobs API — Search public LinkedIn jobs from a required location and optional filters, returning normalized role, company, place, employment, experience, remote, salary, and timing fields.
- LinkedIn Search People API — Discover candidate public profiles from LinkedIn people-search URLs, returning normalized identity, description, images, location, website, account signals, and available metrics.
- LinkedIn Search Posts API — Discover Google-indexed public LinkedIn posts by keyword and optional date string, returning normalized content, authors, media, tags, timestamps, and visible engagement.