Posting to LinkedIn through the API

Long-form, and a different voice entirely. The request shape is the same one every network here uses — only the limits on this page change.

LinkedIn publishes for anyone today. Connect an account and the request below works as written.

Connecting a LinkedIn account

Needs a LinkedIn app with the Share on LinkedIn product. Once connected, we hold the credential and keep it alive; your code only ever sends the API key.

The limits we enforce before publishing

What pre-flight rejects, verbatim

A request that breaks a LinkedIn rule comes back as a 422 naming the network and the number — before anything is scheduled, not after the other networks published. The error strings are these:

• 3132 chars — LinkedIn allows 3000.
• 11 attachments — LinkedIn allows 9.
• Video is 20m — LinkedIn allows 10m.

The request

curl -X POST https://attentionpilot.com/api/v1/posts \
  -H "Authorization: Bearer $PILOT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "caption": "Written for LinkedIn, under 3000 characters.",
    "accounts": ["linkedin"]
  }'

Omit schedule for the next free queue slot, send "now" to publish immediately, or send an ISO timestamp.

When LinkedIn fails

Each network is delivered on its own. A revoked token or a rejected upload on LinkedIn never blocks your other targets: the post returns "partial", the LinkedIn target carries the error text, and you can retry just this delivery.

Worth knowing

• ✓3,000 characters
• ✓Up to 9 images
• ✓Video up to 10m

The same call reaches the rest