LinkedIn Company Posts
LinkedIn Company Posts are public updates surfaced around organization pages with text, publisher identity, media, publication time, topics, and visible engagement. These records support communication monitoring, content review, media analysis, and comparison across selected organizations and time windows.
Features
- Company-page discovery anchorUse one or more public LinkedIn /company/ URLs to discover posts associated with each selected organization page.
- Publisher contextReturn a normalized author object so company association remains distinct from the person or publisher identified on an individual post.
- Content and media signalsCombine post text, attached media, hashtags, mentions, publication time, and the original post URL in each record.
- Visible engagement snapshotExpose available likes, comments, shares, and views as collection-time counters rather than inferred reach or business outcomes.
- Optional provider date valuesForward non-empty start_date and end_date strings with every input URL without imposing a local format, ordering, inclusiveness, or time-zone interpretation.
Parameters
| Parameters | Required | Description |
|---|---|---|
urls | Required | Required list of public http or https LinkedIn company-page URLs. Each host must be linkedin.com or a LinkedIn subdomain, and its path must begin with /company/. |
start_date | Optional | Optional non-empty provider date value forwarded for each URL. YYYY-MM-DD is the documented example, but the service does not parse its format, inclusiveness, or time zone. |
end_date | Optional | Optional non-empty provider date value forwarded for each URL. The service does not check its format or require it to follow start_date. |
results_limit | Optional | Optional integer cap applied separately to each input URL. The default is 100, the minimum is 1, and the maximum is 2000. |
How to Use
Submit company-page URLs with any optional date values, then poll the asynchronous task and read each cursor page.
- Prepare public LinkedIn URLs whose paths begin with /company/.
- POST urls, optional start_date and end_date strings, and results_limit to /v1/linkedin/company-posts; save task_id.
- Poll /v1/tasks/{task_id} until the task reaches succeeded or failed.
- Read data.results.items and continue with next_cursor whenever has_more is true.
curl -X POST "https://api.socq.ai/v1/linkedin/company-posts" \
-H "Authorization: Bearer $SOCQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{"urls":["https://www.linkedin.com/company/microsoft/"],"start_date":"2026-01-01","end_date":"2026-06-30","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 timelines: Organize post text, publication times, source URLs, and publisher identity into reviewable timelines for selected company pages.
- Topic and media review: Use hashtags, mentions, text, and media references to examine recurring public subjects and content formats within the returned sample.
- Comparable engagement snapshots: Compare visible likes, comments, shares, and views across returned posts when dates, limits, and collection times are held consistent.
- Follow-up content selection: Use post IDs, URLs, authors, text, and counters to select specific records for later comment or creative analysis.
Pro Tips
- Validate every input as a complete LinkedIn /company/ URL before submitting a multi-page task.
- Treat start_date and end_date as provider-defined strings; use YYYY-MM-DD consistently, but do not assume local validation, inclusiveness, or ordering.
- Keep dates, results_limit, and collection timing consistent when comparing multiple company pages.
- Inspect author and post URL on every record because association with a company page does not guarantee company-page authorship.
- Deduplicate by stable post id or URL when overlapping pages or repeated runs surface the same post.
- Store media links defensively because public assets can redirect, expire, or become unavailable after collection.
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 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 Profile Posts API — Discover public posts associated with LinkedIn profile URLs, with author context, media, hashtags, timestamps, and visible engagement.
- 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.