Skip to content

Reply to Comment API

The Reply to Comment API lets you post a reply to an existing comment across Facebook, Instagram, LinkedIn, YouTube, Threads, and Twitter/X. Use it when a conversation is already underway and you need to respond in place, rather than starting a new top-level comment. The operation is Reply to a Comment, sent as POST /v1/comments with a JSON body containing platform, accountId, commentId, and text.

Reply to Comment API operation summary

Reply to a Comment adds a response beneath an existing comment. On Threads, the identifier supplied in commentId should be the thread ID for Threads. Before sending, confirm that the accountId you intend to use is the integration ID obtained from list_integrations, that the platform value matches the account and comment you are targeting, and that text contains the exact reply you want posted. A successful response returns success set to true and a new commentId identifying the reply that was created, so store that value if you need to reference, moderate, or follow up on the reply later.

Request contract

Send the request as POST /v1/comments to the origin-modular base URL, with the x-access-key header and Content-Type set to application/json. The request body is a single JSON object with four required string fields. Do not omit any of them: platform selects the social platform, accountId selects the connected integration account, commentId identifies the comment to reply to, and text carries the reply content. See the Reply request headers and Reply request example for the complete worked request and the Successful reply response example for the response shape.

Input contract and platform field map

The input contract table below maps each required body parameter to its type, requiredness, allowed values, and description. Validate every field before sending: platform must be one of the listed enum values, accountId must be a valid integration ID from list_integrations, commentId must be the platform comment ID except on Threads where it is the thread ID for Threads, and text must be present as the reply text. Because the source supplies no error response or status-code contract, this page does not invent error codes; treat any non-success outcome as unresolved until an error contract is supplied.

Validation and failure checklist

Use the validation and failure checklist to check your call before and after sending. Confirm the method is POST and the path is exactly /v1/comments, confirm both headers are present, confirm all four body fields are non-empty strings, confirm platform is a supported enum value, confirm accountId came from list_integrations, and confirm commentId semantics for the chosen platform, especially the Threads thread ID exception. After sending, check that the response contains success as true and capture the returned commentId. If success is not true, or the new commentId is missing, do not assume the reply was created; record the request you sent and the response you received for diagnosis, since no retry, idempotency, or error-handling behavior is defined in the available contract.

Input contract — POST /v1/comments body parameters
ParameterTypeRequiredAllowed valuesDescription
platformstringYesfacebook, instagram, linkedin, youtube, threads, twitterSocial platform to reply on.
accountIdstringYesIntegration ID from list_integrationsConnected account integration ID.
commentIdstringYesPlatform comment ID; thread ID for ThreadsComment to reply to; for Threads, the thread ID for Threads.
textstringYesReply text stringReply text to post.

Exact source contract; origin modularized as {{API_BASE_URL}}.

Response contract
FieldType (example-derived)Description
successboolean (example-derived: true)True when the reply was created successfully.
commentIdstring (example-derived)ID of the newly created reply comment.

Exact source response shape; field types inferred from example values, not declared in source.

Reply request example
POST {{API_BASE_URL}}/v1/comments
x-access-key: YOUR_ACCESS_KEY
Content-Type: application/json

{
  "platform": "instagram",
  "accountId": "INTEGRATION_ID",
  "commentId": "COMMENT_ID",
  "text": "An example comment."
}
Successful reply response example
{
	"success": true,
	"commentId": "NEW_COMMENT_ID"
}
Contract example 1
POST /v1/comments
x-access-key: YOUR_ACCESS_KEY
Content-Type: application/json
Contract example 2
{
	"platform": "instagram",
	"accountId": "INTEGRATION_ID",
	"commentId": "COMMENT_ID",
	"text": "An example comment."
}