Social platforms

List posts published by a LinkedIn company page · LinkedIn API

GET/linkedin/companies/{slug}/posts
$$min $0.01

Return posts published from a LinkedIn company page by URL slug as a cursor-paginated list. This operation is capacity-limited; the gateway makes up to 3 total attempts for transient failures.

Using ChatGPT, Claude Code or another client? See the setup steps

Request
curl https://api.unifapi.com/linkedin/companies/{slug}/posts \
  -H "Authorization: Bearer $UNIFAPI_KEY"

Parameters

slugpathrequired
The slug path parameter for this LinkedIn operation. Use the URL-visible slug or id described in the docs.
cursorquery
The cursor query parameter for this LinkedIn operation. Use the URL-visible slug or id described in the docs.
sort_byquery
The sort_by query parameter for this LinkedIn operation. Use the URL-visible slug or id described in the docs.
The parameter for this LinkedIn operation. Use the URL-visible slug or id described in the docs.
Overview

This operation is part of the LinkedIn API in the social platforms category. It uses the same Bearer token, request tracing, error model, and billing envelope as every UnifAPI endpoint, so agents can switch between platforms without custom per-vendor glue code.

Use it when a workflow needs LinkedIn public data alongside other social networks, but should still keep one API key, one account balance, and one predictable JSON contract.

Common agent workflows

  • Fetch canonical public LinkedIn content for summarization, ranking, monitoring, or enrichment.
  • Attach engagement, author, media, and source metadata to an agent workflow.
  • Give an AI agent a stable LinkedIn data source without building a per-platform integration.
  • Normalize LinkedIn responses into the same UnifAPI envelope used across the catalog.
Response shape

Unified envelope, platform-native fields

  • List-style responses return `data` as an array of top-level records plus optional `pagination` for continuation tokens or cursors.
  • The operation has a 12 credits ($0.01) minimum charge, so `billing.records_charged` can be higher than the visible records returned.
  • If the workspace balance cannot cover every result, the response can be truncated and `billing.truncated_due_to_balance` tells the caller why.

Response status codes

200400401402404429500502503

Billing

This operation charges 1 credit per billable record, with a 12 credits ($0.01) operation minimum. Public responses include billing metadata with credits charged, records charged, and remaining workspace balance. Incorrect Credit deductions caused by platform failures can be restored as billing corrections.

Errors and retries

Authentication, validation, rate-limit, not-found, and provider errors use the unified UnifAPI error format. Agents should log `request_id`, retry only retryable failures, and treat invalid API keys, disabled keys, and expired keys as the same public `unauthorized` error type.

Response fields

Fields on each record in data

A successful List posts published by a LinkedIn company page call returns data as an array; each record carries these fields (12 of 13 shown — the docs list the full schema).

idstring
share_urnstring
post_typestring
ugc | activity | share | ...
textstring
urlstring
create_timeinteger
Unix epoch seconds
created_atstring
Original ISO timestamp
like_countinteger
comment_countinteger
share_countinteger
reactionsobject[]
authorobject
Heterogeneous post author — may be a person or a company. `username` is non-null only for people.
Related endpoints

More LinkedIn operations

Combine endpoints from the same platform, then join the results with other UnifAPI categories without changing authentication or response parsing.