---
title: "Reply to a comment"
method: POST
path: "/v1/{account_id}/posts/{post_id}/comments/{comment_id}"
tags: ["Comments"]
---

# Reply to a comment

`POST /v1/{account_id}/posts/{post_id}/comments/{comment_id}`

## Request

- Base URL: `https://api.curviate.com`
- URL: `https://api.curviate.com/v1/{account_id}/posts/{post_id}/comments/{comment_id}`
- Auth: HTTP bearer

Creates a reply under a top-level comment. Same path as update_comment, POST creates a new reply, PATCH edits the target comment itself. Returns the full created Comment (reply) object.

## Path parameters

- `account_id` string, required
- `post_id` string, required
- `comment_id` string, required

## Request body

- object
  - `text` string, required: Comment body text (1-1250 chars). Inline @mentions live in the text (e.g. "@ACoAA..."). Not stored or logged.
  - `comment_as` string: Publish as another user or company page id, the account must administer it.
  - `attachments` object[]: At most one base64 image attachment (LinkedIn's one-image-per-comment limit). Platform rendering of comment attachments is not guaranteed.
    - `content` string, required: Base64-encoded file bytes.
    - `content_type` string, required: Attachment MIME type (e.g. image/png).
    - `filename` string, required: File name for the attachment.

## Response `201`

Reply published successfully. Returns the full created Comment (reply) object. Same path as update_comment, POST creates a reply, PATCH edits the target comment.

- object: A LinkedIn comment or reply (content pass-through, text and attachments are never stored).
  - `object` 'comment': Response type discriminator.
  - `id` string: Comment identifier (bare numeric string), use this as the comment_id path param on sub-resource endpoints.
  - `created_at` string, nullable: ISO-8601 UTC datetime the comment was created, or null.
  - `text` string, nullable: Full comment text (content pass-through, never stored).
  - `reply_count` number: Total reply count on this comment.
  - `reactions` object[]: Per-reaction-type count buckets.
    - `type` 'like' | 'celebrate' | 'support' | 'love' | 'insightful' | 'funny': Reaction type (unified lowercase enum).
    - `count` number: Count of this reaction type on the comment.
  - `reaction_count` number: Total reaction count on this comment, the sum of reactions[].count.
  - `author` object: Author of the comment. Two shapes reach this field, so read the display name as `display_name` when it is present and `name` otherwise.
    - `id` string: LinkedIn profile identifier.
    - `object` string: Author entity discriminator, on the shape that carries one.
    - `type` string: Author entity type (for example individual or organization), on the shape that carries one.
    - `display_name` string: Author's display name. Absent on the shape that carries `name` instead.
    - `name` string: Author's display name. Absent on the shape that carries `display_name` instead.
  - `can_reply` boolean: true if the authenticated account can reply to this comment.
  - `can_react` boolean: true if the authenticated account can react to this comment.
  - `is_sender` boolean: true if the authenticated account authored this comment.
  - `attachments` object[]: Attachment metadata (inline only).
    - `id` string: Attachment identifier.
    - `mimetype` string: Attachment MIME type.
    - `type` string: Attachment type (e.g. img, file).
    - `filename` string: Original filename, when known.
    - `file_size` number: File size in bytes, when known.
  - `safety_warning` SafetyWarning: Present on a successful response when this account crossed an account-safety ceiling while the affected budget row is on the default warn posture. The action still happened. Field-identical to the BUDGET_EXHAUSTED error body except that blocked is false and hint.message describes the outcome, so one branch handles both postures and switching the account to enforce is a configuration change rather than a client rewrite.
    - `row` string, nullable, required: The budget row that breached, for example profile_views or pending_invites. Null when the breach is not about a row: an activity_window warning on an action that spends no budget of its own (editing a message, dismissing a notification, a Recruiter or Sales Navigator admin action) is still governed by the hours the account works in. Read hint.parameter for what to change; whenever this is null it names posture, because the activity window edges are set per action type and this action has none, so the levers that reach it are the account timezone and posture.
    - `reset_at` string, nullable, required: The instant the refusal lifts: the window roll on a ceiling refusal, the next window open on an activity-window one. Null in the two cases no clock frees, the pending_invites gauge and InMail credits (row inmail).
    - `hint` object, required
      - `parameter` string, required: The settable parameter on PATCH /v1/{account_id}/safety-policy.
      - `message` string, required: What the condition is and what changing that parameter would do. This is the one field whose text differs from the BUDGET_EXHAUSTED refusal: here it says the action went through, and on a ceiling breach how far past the ceiling this row now stands, rather than telling you to set posture to warn when it already is. Branch on parameter, reason and blocked, never on this text.
    - `reason` 'ceiling' | 'activity_window', required: Which rule was crossed. ceiling means the row's configured limit is spent; activity_window means the account is outside the hours it works in, which is a different fact with a different remedy. hint.parameter names the right setting for each.
    - `blocked` boolean, required: Always false here. True on the BUDGET_EXHAUSTED refusal carrying the same payload.

## Other responses

- `400`: Missing required field, empty text, more than one attachment, or an unrecognized field in the request body.
- `401`: Missing or invalid API key.
- `404`: The account_id does not belong to this tenant (ACCOUNT_NOT_FOUND), or the comment was not found (RESOURCE_NOT_FOUND). An id whose connection was replaced or removed also stops resolving here, and it is already absent from the list, so re-read `GET /v1/accounts` for the current id.
- `413`: Payload too large. Three triggers, smallest first: the platform's own ceiling on total request size, which rejects bodies from roughly 1 MB and is the one most callers hit; then the caps enforced here, 5 MiB per attachment and 9 MiB for the whole request body. Base64 inflates a file by about 33 percent, so a 5 MiB file costs about 6.7 MiB of the body budget. Send fewer or smaller attachments; retrying the same request unchanged will not help.
- `415`: Unsupported media type, this endpoint accepts application/json only.
- `422`: The platform rejected the reply (e.g. content policy). Conservative mapping, outage-indistinguishable errors stay 502.
- `429`: Rate limited, slow down and retry after the hinted delay.
- `500`: Internal error.
- `502`: A temporary error occurred. Please try again.
- `503`: Service unavailable.
- `504`: Gateway timeout.

---

[API](https://skmtc.dev/curviate/apis/curviate-api.md) · [All operations](https://skmtc.dev/curviate/apis/curviate-api/llms.txt) · [OpenAPI document](https://skmtc.dev/curviate/apis/curviate-api/revisions/eab848801d95?raw)