LinkedIn Integration

These endpoints manage personal LinkedIn posting targets — the destinations the user can cross-post to via their own linked LinkedIn identity. For organization-bound LinkedIn (a shared org credential and company-page assignments), see Organizations.

A target is one of three things:

1. The user's personal LinkedIn account (linked via OAuth)
2. An organization page assigned to the user with an active org connection
3. A personal company page — a LinkedIn company page the user administers, discovered through their own LinkedIn connection (requires the rw_organization_admin scope)

Endpoint table

Target shape

{ "kind": "personal", "label": "Alice Example", "avatarUrl": "https://..." }

{
  "kind": "orgPage",
  "pageId": "<OrgLinkedInPage uuid>",
  "linkedInPageId": "12345678",
  "label": "Acme Corp",
  "logoUrl": "https://..."
}

{
  "kind": "personalPage",
  "personalPageId": "<LinkedInPersonalPage uuid>",
  "linkedInPageId": "87654321",
  "label": "Alice's Studio",
  "logoUrl": "https://..."
}

pageId (org) and personalPageId (personal) are the InterlinedList record IDs to use in the linkedInTargets field when posting via POST /api/messages. linkedInPageId is LinkedIn's own page identifier. If the same LinkedIn page is reachable both as an org page and as a personal page, only the orgPage form is returned.

Listing available targets

GET /api/linkedin/targets

{
  "targets": [
    { "kind": "personal", "label": "Alice Example", "avatarUrl": null },
    { "kind": "orgPage", "pageId": "...", "linkedInPageId": "12345678", "label": "Acme Corp", "logoUrl": null },
    { "kind": "personalPage", "personalPageId": "...", "linkedInPageId": "87654321", "label": "Alice's Studio", "logoUrl": null }
  ]
}

Saved preferences

GET /api/linkedin/posting-targets

{
  "targets": [
    { "kind": "personal", "label": "Alice Example", "avatarUrl": null, "enabled": true },
    { "kind": "orgPage", "pageId": "...", "linkedInPageId": "12345678", "label": "Acme Corp", "logoUrl": null, "enabled": false },
    { "kind": "personalPage", "personalPageId": "...", "linkedInPageId": "87654321", "label": "Alice's Studio", "logoUrl": null, "enabled": true }
  ],
  "orgScopeMissing": false
}

Preferences are a client-side default for the composer's target picker — they are not enforced when posting. Server-side authorization for POST /api/messages always re-validates against the user's actual assignments and linked identities.

orgScopeMissing is true when the user has a personal LinkedIn connection but the stored scope does not include rw_organization_admin. The fix is to reconnect LinkedIn via GET /api/auth/linkedin/authorize?link=true.

Updating preferences

PUT /api/linkedin/posting-targets
Content-Type: application/json

{
  "targets": [
    { "kind": "personal" },
    { "kind": "orgPage", "pageId": "<OrgLinkedInPage uuid>" },
    { "kind": "personalPage", "personalPageId": "<LinkedInPersonalPage uuid>" }
  ]
}

Targets in the body become enabled; all others become disabled. An empty array disables every target. Duplicates are removed. Each target is validated against what the caller can actually post to — invalid entries return 400.

Re-syncing personal company pages

POST /api/linkedin/sync-pages

{
  "pages": [
    {
      "id": "<LinkedInPersonalPage uuid>",
      "linkedInPageId": "87654321",
      "pageName": "Alice's Studio",
      "pageLogoUrl": "https://...",
      "lastSyncedAt": "2026-06-12T00:00:00.000Z"
    }
  ]
}

Pages no longer administered are removed; new and existing pages are upserted. Errors:

Pages are also discovered automatically by the OAuth callback when the account is linked with the org scope. This endpoint is for refreshing the list afterwards.