Feature request: LinkedIn first comment via Typefully Public API

To: Typefully product / API team
From: Howard Peng · xWatchlist (@xWatchlist_ / social set #319800)
Date: 2026-07-14
Priority: High for multi-platform automation pipelines
Related UI feature: Publish a LinkedIn Comment with Your Post (2025-01-23)

1. Summary

Please expose LinkedIn first comment (the public author comment that publishes with the post) on the Public API v2 create/update draft endpoints.

Today this is available in the Typefully UI (“Add LinkedIn comment”) but not in the API. Automation pipelines can create and schedule LinkedIn drafts, but cannot attach the first comment without a human opening the editor.

2. Why we need it

Product context

xWatchlist is an automated content pipeline:

Generate insight + stat card from a public xAI employee cohort
Review in Telegram
Publish via Typefully on one social set (#319800) as three independent drafts:
- A · X — EN + image + quote_post_url
- B · LinkedIn — EN + image
- C · Threads — Traditional Chinese + image; source URL as thread post #2

LinkedIn-specific constraint

Platform	How we attach source today
X	`quote_post_url` on the post
Threads	`posts[1]` = `來源 https://x.com/...` (thread)
LinkedIn	No quote field; `posts[]` max length = 1

Putting Source: https://x.com/... in the post body works but is suboptimal for LinkedIn ranking. Typefully’s own changelog recommends moving links to the first comment for this reason.

We already use the UI pattern successfully:

[Author comment]
Source: https://x.com/{handle}/status/{id}

We need the same thing without leaving the API path.

3. What we probed (2026-07-14)

Against POST /v2/social-sets/{id}/drafts with a valid API key on set #319800:

Payload attempt	Result
`platforms.linkedin.first_comment`	`422` Extra inputs not permitted
`platforms.linkedin.comment`	`422`
`platforms.linkedin.settings.*` (various)	`422` (LinkedInSettings is empty / `additionalProperties: false`)
`platforms.linkedin.posts[0].first_comment`	`422`
`platforms.linkedin.posts` with 2 items	`400` “LinkedIn only supports single posts”
Draft-level `first_comment` / `linkedin_comment`	`422`

Observed LinkedIn post shape from GET (allowed fields):

text
media_ids
linkedin_reshare_urn
hide_link_preview

Conclusion: First comment is UI-only; not represented in Public API v2 schema today.

Note: Draft comment-threads endpoints (/comment-threads) are for in-editor collaboration, not for public LinkedIn author first comments. Those do not solve this use case.

4. Requested API shape

Any of the following would work. Option A is preferred (mirrors the UI mental model).

Option A — platform setting (preferred)

POST /v2/social-sets/{social_set_id}/drafts
PATCH /v2/social-sets/{social_set_id}/drafts/{draft_id}

{
  "platforms": {
    "linkedin": {
      "enabled": true,
      "posts": [
        {
          "text": "Lean AI-native teams are real: …",
          "media_ids": ["…"]
        }
      ],
      "settings": {
        "first_comment": {
          "text": "Source: https://x.com/spacexai/status/2076692402442846289"
        }
      }
    }
  },
  "publish_at": "next-free-slot"
}

Option B — post-level field

{
  "platforms": {
    "linkedin": {
      "enabled": true,
      "posts": [
        {
          "text": "…",
          "media_ids": ["…"],
          "first_comment": {
            "text": "Source: https://x.com/…/status/…"
          }
        }
      ]
    }
  }
}

Response / GET symmetry

Please return the same field on:

GET /v2/social-sets/{id}/drafts/{draft_id}
list drafts preview (optional: truncated first-comment flag)

Behavior should match UI:

Comment is stored with the draft while draft / scheduled
On publish, Typefully posts the LinkedIn update then the author first comment
Editable until publish; ignored or 409 after published (same as other immutable fields)

5. Acceptance criteria

Create LinkedIn-only draft with first comment via API
PATCH first comment on draft/scheduled drafts
Clear first comment (null / empty)
On publish_at: "now" / scheduled publish, first comment appears as Author comment under the post (same as UI)
OpenAPI / docs updated; field documented as LinkedIn-only
(Nice) Support plain URL + optional leading label (Source:)

6. Workaround we use until then

API creates LinkedIn draft with link-free body + image
API writes paste-ready text into scratchpad_text:
```
Source: https://x.com/{handle}/status/{id}
```
Operator opens Typefully → Add LinkedIn comment → paste → schedule/publish

This keeps rank-friendly posts but reintroduces a human step we would like to remove.

7. Who we are / volume

Product: xWatchlist (cohort signal → multi-surface posts)
Social set: #319800 (xWatchlist) — X + LinkedIn + Threads
Cadence: low volume (a few drafts/day), high need for deterministic automation
Happy to beta-test a preview field or private flag on our key

8. Contact

Howard Peng
Email / Typefully account: as registered on the #319800 workspace
Repo note (internal): docs/reference/typefully-linkedin-first-comment-api-request.md

Thank you — the UI first-comment feature is excellent; exposing it on API v2 would unblock multi-platform “source in comment / thread” pipelines the same way quote_post_url and multi-posts[] already do for X and Threads.

howardpen9/typefully-linkedin-first-comment-api-request.md

Select an option

No results found