Skip to content

LinkedIn Posting API

The LinkedIn Posting API gives product teams a single route for LinkedIn publishing, so each team does not need to build and maintain its own LinkedIn-specific connection.

Text Post Request
POST {{API_BASE_URL}}/v1/posts
x-access-key: YOUR_API_KEY
Content-Type: application/json
{
    "content": "A short example update.",
    "platforms": [
      {
        "platform": "linkedin",
        "accountId": "li_123"
      }
    ],
    "publishNow": true
}
Illustrative request
Example line 1

POST {{API_BASE_URL}}/v1/posts

Illustrative request
Example line 2

x-access-key: YOUR_API_KEY

Illustrative request
Example line 3

Content-Type: application/json

Text updates, still images, video, and article shares can be directed to personal profiles or company pages. Managed OAuth covers account linking and token upkeep. Immediate delivery, deferred delivery, and Cross-Platform Publishing are all available through the same approach.

LinkedIn Posting API: What It Publishes and Where It Publishes To

A single publishing route for LinkedIn removes the need for each product team to build and maintain its own LinkedIn-specific connection. Through the LinkedIn Posting API, text updates, still images, video, and article shares can be directed to personal profiles or company pages. Managed OAuth covers account linking and token upkeep. Immediate delivery, deferred delivery, and Cross-Platform Publishing are all available through the same approach.

Add Social Media to Your Product in Three Steps

One connection supports publishing, scheduling, analytics, comment handling, and messaging across networks. First, create an account and obtain an API key. Second, connect that key inside your application so publishing, scheduling, analytics, comments, and messages flow through one interface. Third, enable additional networks for your users without constructing a separate integration for each one. The Text Post Request and Text Post Response examples below show the exact captured contract.

Captured Contract: POST /v1/posts Text-Post Request and 202 Response

Every format shares one endpoint; only the fields relevant to that format change. The captured text-post example sends POST {{API_BASE_URL}}/v1/posts carrying content, a platforms array with platform and accountId, and publishNow set to true. A successful text post returns a 202 response carrying success, status, postId, and a platforms array with platform, success, and platformPostUrl. Consult the Field Map and Input Contract tables below before implementing, and distinguish captured fields from prose-described fields that require verification. For a worked check, send the Text Post Request exactly as shown, confirm the response status is 202, confirm success is true and status is published, store postId for later lookup, and store platformPostUrl as the LinkedIn destination. If any of those fields is missing, treat the request as failed and inspect the platform entry rather than assuming delivery.

Everything You Need for LinkedIn Posting

Profile and Company Page Posting sends to a personal LinkedIn profile or to an organization page, with the connected account ID choosing the destination. Rich Media Support covers still images and video alongside text, with the media upload process handled for you. Article Sharing covers links and articles with preview cards, driven by an article URL plus optional title and description. Scheduled Posting lets you pick a date, time, and timezone while still calling the same publishing endpoint. Cross-Platform Publishing sends one request to LinkedIn plus other supported networks, with optional per-platform content overrides. Managed OAuth links LinkedIn accounts while OAuth and token management are handled for you.

Decision Criteria: Profile vs Company Page, Publish Now vs Scheduled, Single vs Cross-Platform

Pick a personal profile when the post should appear under an individual name, and pick a company page when it should appear under an organization; the connected accountId decides the destination either way. Pick publishNow for immediate delivery and scheduledFor for Scheduled Posting, adding an IANA timezone when the scheduled moment must be interpreted in a particular zone. Pick a single-platform request when only LinkedIn matters, and pick Cross-Platform Publishing when LinkedIn plus other supported networks should receive the post in one request, using per-platform overrides when wording or media must differ by network. For Article Sharing, supply articleUrl and add articleTitle and articleDescription only when you want to override the preview text. For visibility, use PUBLIC or CONNECTIONS as described in the source, and remember that organization pages can be tagged while tagging an individual profile is unavailable through this route.

Failure Matrix and Checks Before You Retry

If a platform entry is missing or accountId does not identify a connected LinkedIn account, do not retry blindly; verify the connected account first. If you attempt to tag an individual profile, expect that to be unavailable and change the tag to an organization page or remove it. If media exceeds the stated limits, reduce the number or size of images, or replace multiple videos with one MP4 video within the stated limit. If an article share lacks a usable articleUrl, the preview cannot be built, so validate the URL before sending. If a scheduled post uses an ambiguous timezone, supply an IANA timezone so the date and time are interpreted consistently. After any failure, check the per-platform success entry in the response before resending, so a successful LinkedIn delivery is not duplicated by a retry aimed at another platform.

Ship LinkedIn Posting in Any Stack

Node applications, no-code automations, and AI agents can all drive the same publishing workflow through one interface. Developer stacks can use typed SDKs and predictable REST APIs, including REST plus cURL. No-code workflows can trigger publishing from tools such as Zapier, Make, and n8n. AI agents and MCP workflows can publish, schedule, and interact with social workflows through a hosted MCP server, agent skills, and an OpenAI tool-calling schema. Keep the endpoint, field names, and response handling identical across stacks; only the client library and trigger mechanism should change.

Field Map for Captured POST /v1/posts Text-Post Contract
FieldLocationType / Value in ExampleRequiredness in Captured ExamplePurpose
contentRequest bodystring: "Excited to share our latest product update!"Present in captured examplePost text
platformsRequest bodyarray of objectsPresent in captured exampleTarget platforms and accounts
platforms[].platformRequest bodystring: "linkedin"Present in captured exampleSelects LinkedIn
platforms[].accountIdRequest bodystring: "li_123"Present in captured exampleSelects the connected profile or company page account
publishNowRequest bodyboolean: truePresent in captured examplePublishes immediately in the example
success202 response bodyboolean: truePresent in captured responseOverall success flag
status202 response bodystring: "published"Present in captured responsePost status
postId202 response bodystring: "post_abc123"Present in captured responseIdentifier for the created post
platforms[].platform202 response bodystring: "linkedin"Present in captured responsePer-platform result
platforms[].success202 response bodyboolean: truePresent in captured responsePer-platform success flag
platforms[].platformPostUrl202 response bodystring URLPresent in captured responseLinkedIn URL for the published post

Captured text-post contract only; other formats are prose-described and require verification.

Input Contract: Captured vs Prose-Described Fields
FieldStatusSource BasisNotes
content, platforms, accountId, publishNowCapturedCaptured request code blockExact field names preserved
success, status, postId, platformPostUrlCapturedCaptured 202 response code blockExact field names preserved
articleUrlProse-describedFAQ: use articleUrl for link-share previewOptional articleTitle and articleDescription described alongside it
scheduledForProse-describedFAQ: use /v1/posts with scheduledForOptionally an IANA timezone
Visibility PUBLIC / CONNECTIONSProse-describedFAQ visibility answerCompany-page mentions supported; personal-profile mentions not supported

Prose-described fields are not captured schemas; verify against owned implementation before publication.

Failure Matrix
ScenarioCheckAction
Missing or wrong accountIdConfirm the connected LinkedIn account for the intended profile or company pageCorrect accountId before retrying
Personal-profile mentionMentions support company pages; personal-profile mentions are not supportedUse a company-page mention or remove the mention
Too many or oversized imagesUp to 9 images, up to 10 MB eachReduce count or size
Video format or sizeOne MP4 video, up to 5 GBReplace with one MP4 within the limit
Article share without articleUrlarticleUrl creates the previewSupply a valid articleUrl; add articleTitle/articleDescription only as overrides
Ambiguous scheduled timescheduledFor with optionally an IANA timezoneSupply an IANA timezone
Partial cross-platform failureInspect per-platform success entriesRetry only the failed platform entry

Derived from source-stated limits and constraints; verify error shapes against owned implementation.

Frequently asked questions

What can I publish to LinkedIn through the LinkedIn Posting API?

Text updates, still images, video, and link-based article posts can be sent to an individual profile or to an organization page.

Can I post to both LinkedIn profiles and company pages?

Both kinds of destination are covered. The connected account you select decides whether delivery goes to a personal profile or to an organization page.

What are the LinkedIn media limits?

Still-image posts accept a maximum of nine files, each no larger than 10 MB. Video posts accept a single MP4 file, no larger than 5 GB.

Can I share articles or links?

Link posts are supported. Supply articleUrl to generate the preview, and optionally supply articleTitle plus articleDescription when you want custom preview wording.

Can I control visibility and mentions?

Audience scope can be set to PUBLIC or CONNECTIONS. Organization pages can be tagged; tagging an individual profile is unavailable through this route.

Can I schedule LinkedIn posts?

Deferred delivery is supported on /v1/posts through scheduledFor, with an IANA timezone available for zone-specific interpretation.

What can I build with the LinkedIn Posting API?

Typical applications include publishing features inside SaaS products, social-media management dashboards, automated content pipelines, and agent-driven workflows.

Can I use the LinkedIn Posting API for LinkedIn content workflows?

Agency teams can automate client publishing, content teams can adapt existing material for LinkedIn, and product teams can embed publishing directly inside their own software.

Text Post Response (202)
{
    "success": true,
    "status": "published",
    "postId": "post_abc123",
    "platforms": [
      {
        "platform": "linkedin",
        "success": true,
        "platformPostUrl": "https://www.linkedin.com/feed/update/urn:li:share:123456"
      }
    ]
}