Skip to main content
POST
Create LinkedIn comment

Authorizations

Authorization
string
header
required

Access token issued by gtm.service.id. Its access_identity claim carries team_sid, actor_sid and actor_type, and that team scope is authoritative.

Team-SID
string
header
required

Team scope for tokens that do not carry one. Ignored when the token already names a team.

Body

application/json

Request body of create_linkedin_comment.

linkedin_account_sid
string
required

LinkedIn account sid (ln_ac_…), the authoring account. Identity-bound: REQUIRED, posts publish AS this account.

Required string length: 18
Pattern: ^ln_ac_
entity_urn
string
required

The target handle, in the wire's full social-thread vocabulary (2026-08-21): a post urn in any of the four families - urn:li:activity: (member posts), urn:li:share:, urn:li:ugcPost: (company pages and newsletters), urn:li:groupPost:- (group threads) - or a COMMENT key to target a comment, in either form: public urn:li:comment:((activity|share|ugcPost|groupPost):,) or the fsd urn:li:fsd_comment:(,) LinkedIn's own responses carry (normalized before the wire). All pass verbatim; a malformed urn is refused 422 before any dispatch. A post URL is also accepted when the id is in it: the feed permalink and the share link (/posts/-activity--) are both converted locally. A link WITHOUT an id (a shortlink, a bare slug URL) is refused 422 entity_urn_not_resolvable: reading those means opening the page, so call get_activity_urn_by_url first rather than have a write verb open a page silently. The post does NOT need to be tracked or owned by us. Renamed from activity_urn on 2026-07-30; the old name is no longer accepted.

Required string length: 1 - 512
text
string
required

The comment body (caller-supplied, no templates or AI in-app).

Required string length: 1 - 1250
parent_comment_urn
string | null

Reply target: the comment URN to reply under. Omit or null for a top-level comment.

Maximum string length: 512
mentions
object[]

Profile mentions (2026-08-21). Names are matched in text left to right in list order, each search starting after the previous mention. The node computes the character offsets itself.

Response

action success envelope.

success
enum<boolean>
required
Available options:
true
operation
enum<string>
required
Available options:
action
action
string
required

kebab-case verb; matches the route segment.

item
any
required
result
object
required
meta
object
required