LinkedIn API for Posting

The official LinkedIn API

LinkedIn publishes posts through its Posts API (POST https://api.linkedin.com/rest/posts), which replaced the older ugcPosts API. Every call needs a Linkedin-Version header, and versions are retired on a schedule. Posting as a member requires the w_member_social permission; posting as a company page requires w_organization_social, and the member must be an administrator or content admin of that page.

What posting requires

1. Create an app in the LinkedIn Developer Portal and have a super admin of your LinkedIn Page verify it.
2. For personal profiles, add the self-serve "Share on LinkedIn" product, which grants w_member_social.
3. For company pages, request the Community Management API. LinkedIn only grants it to registered legal organizations with a commercial use case, and asks for a business email, legal name, registered address, website and privacy policy.
4. New Community Management apps start on a Development tier (500 calls per app and 100 calls per member per 24 hours) and must finish the integration within 12 months.
5. To lift those limits, apply for the Standard tier with test credentials and a screencast of each use case, including the OAuth flow and posting. If the application is rejected, you have to create a new app to apply again.

Cost: LinkedIn's developer documentation does not list usage fees for the Share on LinkedIn or Community Management products. The cost is the approval process and the engineering time to build and maintain the integration.

Official limits

Common gotchas

• Programmatic refresh tokens are only issued to approved Marketing Developer Platform partners. Without them, members have to sign in again when the 60-day access token expires.
• Even with refresh tokens, the refresh token keeps its original 365-day lifetime, so members must re-authorize once a year.
• API versions are sunset regularly (for example, version 202510 is retired on October 15, 2026), so the integration needs periodic upgrades.
• The Posts API does not scrape URLs for article posts. You have to supply the title, description and thumbnail yourself.
• Reading members' posts and comments needs r_member_social, which is restricted to approved applications.

Post to LinkedIn via API

curl -X POST https://api.publora.com/api/v1/create-post \
  -H "Content-Type: application/json" \
  -H "x-publora-key: sk_YOUR_API_KEY" \
  -d '{
    "content": "We cut our deploy time from 40 minutes to 6. Here is what changed.",
    "platforms": ["linkedin-YOUR_PROFILE_ID"],
    "scheduledTime": "2026-10-06T14:00:00Z",
    "mediaUrls": ["https://example.com/deploy-chart.png"]
  }'

import os
import requests

resp = requests.post(
    "https://api.publora.com/api/v1/create-post",
    headers={"x-publora-key": os.environ["PUBLORA_API_KEY"]},
    json={
        "content": "We cut our deploy time from 40 minutes to 6. Here is what changed.",
        "platforms": ["linkedin-YOUR_PROFILE_ID"],
        "scheduledTime": "2026-10-06T14:00:00Z",
        "mediaUrls": ["https://example.com/deploy-chart.png"],
    },
)
resp.raise_for_status()
print(resp.json()["postGroupId"])

Or let an AI agent post

Connect any MCP client to mcp.publora.com:

• “List my LinkedIn connections, then schedule this announcement to our company page for Tuesday at 14:00 UTC.”
• “Repost urn:li:share:7434685316856377344 from my personal profile tomorrow at 09:00 UTC with a one-line comment.”
• “Comment "Congrats on the launch" on LinkedIn post urn:li:share:7434685316856377344 and react with Celebrate.”