linkedin/
company-posts

Use the LinkedIn Company Posts API to discover public LinkedIn posts from company-page URLs, returning post text, author context, media, hashtags, timestamps, and visible engagement as normalized records.

LinkedIn Company Posts API

Company page discovery
Optional date values
Public post records
1 credit / result
Ready
Ready

Enter parameters and send a request. The task status and normalized results will appear here.

README

By SocQ · Updated

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.

LinkedIn Company Posts API Features

  • Company-page discovery anchorUse one or more public LinkedIn /company/ URLs to discover posts associated with each selected organization page.
  • Publisher contextThe LinkedIn Company Posts API returns 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.

LinkedIn Company Posts API Parameters

ParametersRequiredDescription
urlsRequiredRequired 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_dateOptionalOptional 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_dateOptionalOptional non-empty provider date value forwarded for each URL. The service does not check its format or require it to follow start_date.
results_limitOptionalOptional integer cap applied separately to each input URL. The default is 100, the minimum is 1, and the maximum is 2000.

How to Use the LinkedIn Company Posts API

Give the LinkedIn Company Posts API your company-page URLs with any optional date values, then poll the asynchronous task and read each cursor page.

  1. Prepare public LinkedIn URLs whose paths begin with /company/.
  2. POST urls, optional start_date and end_date strings, and results_limit to /v1/linkedin/company-posts; save task_id.
  3. Poll /v1/tasks/{task_id} until the task reaches succeeded or failed.
  4. 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 true

LinkedIn Company Posts API 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 the post IDs, URLs, authors, text, and counters from the LinkedIn Company Posts API to select specific records for later comment or creative analysis.

LinkedIn Company Posts API 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 you run the LinkedIn Company Posts API against multiple company pages for comparison.
  • 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.

Beyond the LinkedIn Company Posts API, 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 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 Video Transcript API — Turn the captions of LinkedIn videos into plain text from the URLs of the posts that carry them.

Explore other platforms

Combine LinkedIn data with public data from other supported social platforms.

LinkedIn Company Posts API — FAQ

LinkedIn Company Posts API is a programmatic interface for discovering public posts from LinkedIn /company/ page URLs. It returns normalized text, author identity, media, hashtags, mentions, publication time, and visible engagement.

Each value must be a complete http or https URL on linkedin.com or a LinkedIn subdomain, and its path must begin with /company/. Personal /in/ profiles and individual post URLs do not pass this endpoint's URL validation.

Non-empty start_date and end_date strings are forwarded to the discovery provider for every URL. The service does not parse their format, check their order, or define inclusiveness and time-zone behavior, so use consistent YYYY-MM-DD values and interpret results cautiously.

No. A result is associated with the submitted company-page discovery feed, but its normalized author can identify a person, company, or other publisher; inspect author and url before assigning authorship.

results_limit applies independently to each company URL and accepts integers from 1 through 2000. Three URLs with a limit of 20 can therefore store up to 60 posts, subject to public availability and provider behavior.

It means no supported public posts were returned for that URL and date input during that task. It does not prove that the organization has never published, and it should remain distinct from invalid input or task failure.

Each returned post costs 1 SocQ credit, with no base charge. An empty result set has no result charge, and actual usage may exceed the estimate when permitted.