> ## Documentation Index > Fetch the complete documentation index at: https://docs.enginy.ai/llms.txt > Use this file to discover all available pages before exploring further. # Reply to a Social Selling comment > Reply on LinkedIn to one comment of a tracked post, from one of your identities (usually the post author). The reply is posted under the comment’s thread (a reply to a reply goes under the same top-level comment, as on LinkedIn) and never as a separate top-level comment. Same rules as any comment: the identity owner’s consent applies (403 IDENTITY_ENGAGEMENT_CONSENT_DENIED), and a colleague’s identity under manual review answers `status: PENDING_APPROVAL` and waits for its owner. `status: QUEUED` means the reply was dispatched, not that it is live: confirm with `get_social_selling_comment_status` (`POSTED` with its `commentUrn`). Send an `Idempotency-Key` (header or body) so a retry never posts twice. Text 1–3000 characters. Comments marked deleted cannot be answered. > **Required scope:** `SOCIAL_SELLING_WRITE` > > **Rate limit:** 30 requests per minute ## OpenAPI ````yaml https://openapi.enginy.ai/definitions.json post /v1/social-selling/posts/{postId}/comments/{commentId}/replies openapi: 3.1.0 info: title: Enginy API version: 1.0.0 description: Public API for Enginy platform servers: - url: https://openapi.enginy.ai description: Configured server security: [] tags: - name: AI Variables description: >- Manage AI variables and discover the entity fields you can reference in prompts and entity requests. - name: Inbox description: >- Inbox endpoints for listing contact threads, reading thread messages, managing tags, and sending manual replies. - name: Workflows description: >- Build, validate, publish, run, and inspect advanced (graph) workflows, plus the block/condition catalog needed to author a workflow plan. paths: /v1/social-selling/posts/{postId}/comments/{commentId}/replies: post: tags: - Social Selling summary: Reply to a Social Selling comment description: >- Reply on LinkedIn to one comment of a tracked post, from one of your identities (usually the post author). The reply is posted under the comment’s thread (a reply to a reply goes under the same top-level comment, as on LinkedIn) and never as a separate top-level comment. Same rules as any comment: the identity owner’s consent applies (403 IDENTITY_ENGAGEMENT_CONSENT_DENIED), and a colleague’s identity under manual review answers `status: PENDING_APPROVAL` and waits for its owner. `status: QUEUED` means the reply was dispatched, not that it is live: confirm with `get_social_selling_comment_status` (`POSTED` with its `commentUrn`). Send an `Idempotency-Key` (header or body) so a retry never posts twice. Text 1–3000 characters. Comments marked deleted cannot be answered. > **Required scope:** `SOCIAL_SELLING_WRITE` > > **Rate limit:** 30 requests per minute parameters: - schema: type: integer exclusiveMinimum: 0 description: Tracked post id (`id` of the posts list). required: true description: Tracked post id (`id` of the posts list). name: postId in: path - schema: type: integer exclusiveMinimum: 0 description: >- The comment to answer (`commentId` of `list_social_selling_post_comments`). required: true description: >- The comment to answer (`commentId` of `list_social_selling_post_comments`). name: commentId in: path - schema: type: string minLength: 1 maxLength: 255 pattern: ^[A-Za-z0-9._:-]+$ description: >- Same as the body field `idempotencyKey`; ignored when the body sends one. Empty counts as absent. required: false description: >- Same as the body field `idempotencyKey`; ignored when the body sends one. Empty counts as absent. name: Idempotency-Key in: header requestBody: content: application/json: schema: type: object properties: identityId: type: integer exclusiveMinimum: 0 description: >- The identity that replies (usually the post author). It must be in your scope. text: type: string minLength: 1 maxLength: 3000 description: The reply, trimmed. idempotencyKey: type: string minLength: 1 maxLength: 255 pattern: ^[A-Za-z0-9._:-]+$ description: >- Optional; also accepted as the `Idempotency-Key` header (the body wins). The same key with the same request returns the first reply (`replayed: true`); with another request it answers 409 IDEMPOTENCY_KEY_REUSED. required: - identityId - text responses: '201': description: >- Reply dispatched (QUEUED) or waiting for the identity owner (PENDING_APPROVAL) content: application/json: schema: type: object properties: status: type: string enum: - success message: type: string data: type: object properties: scheduledCommentId: type: number status: type: string enum: - QUEUED - PENDING_APPROVAL - POSTED - REJECTED - CANCELLED - DELETED - FAILED - UNCERTAIN publishingPostId: type: number identityId: type: number threadCommentId: type: number threadCommentUrn: type: string repliedToCommentId: type: number replayed: type: boolean required: - scheduledCommentId - status - publishingPostId - identityId - threadCommentId - threadCommentUrn - repliedToCommentId - replayed required: - status - message - data '400': description: Invalid body, the comment was deleted, or the post is not published '403': description: >- Social Selling is not enabled for this workspace. Ask your workspace admin to enable the feature. Also when the identity owner does not allow colleagues to comment from it (`details.code`: IDENTITY_ENGAGEMENT_CONSENT_DENIED). '404': description: >- Post, comment or identity not found in this workspace or outside the caller’s scope '409': description: >- The idempotency key was used for a different request (IDEMPOTENCY_KEY_REUSED) security: - apiKey: [] components: securitySchemes: apiKey: type: apiKey in: header name: x-api-key ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.