LinkedIn

Requirements

Select a connected LinkedIn personal or organization account. GET /accounts includes accountType; check capabilities.publishPosts before writing.

Supported formats

One text post per request. You can target up to 5 text accounts, but any request that includes a LinkedIn account must contain exactly one item in posts. Public API inputs do not support LinkedIn images, videos, or documents.

Publish a post

Account and media UUIDs are illustrative; replace them with real IDs. Set your API key in the POSTEADY_API_KEY environment variable.

curl --request POST "https://www.posteady.com/api/v1/posts" \
  --header "Authorization: Bearer $POSTEADY_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
  "accountIds": [
    "11111111-1111-4111-8111-111111111111"
  ],
  "posts": [
    "Our latest release is ready."
  ]
}'

Confirm success

Inspect each account’s success and postIds, plus summary.failed, in the HTTP 200 response. Other targets or later chain items can fail, so the HTTP code alone does not prove full success.

Scheduling and related tasks

To schedule, send the same platform input to /scheduled-posts with a future scheduledAt and optional timezone. For asynchronous platforms, generate a UUID requestId per operation and retain it for retries.

Schedule and cancel · Read posts and metrics · Retries · MCP tools

Limits and errors

Text allows up to 3,000 Unicode characters. A LinkedIn target rejects thread chains; other targets in the same request can still succeed. A native post ID is a LinkedIn urn:li:share:… or urn:li:ugcPost:…; keep it for a supported repost operation. Reconnect the account if its token expires.

Publishing reference · Troubleshooting