Skip to content

Delete Comment API

The Delete Comment API lets you delete a specific platform comment by sending a DELETE request with the platform comment ID in the path and the platform and integration identifiers as query parameters. Use this reference to build the request correctly, check the documented response for each status code, and apply the platform-specific restrictions before you call the endpoint.

Delete a comment: operation summary and supported platforms

Use DELETE /v1/comments/{commentId} to remove one targeted comment. The request identifies a single comment through commentId, a single platform through platform, and a single integration through accountId, so confirm all three refer to the same comment and integration before sending. Keep a record of the commentId and accountId you used so you can trace the request later.

Authorization: x-access-key header

Send the access key in the x-access-key header on every request. The header name is x-access-key and the value is the token shown as <token> in the contract. Check the header spelling and value before sending, and inspect the documented response statuses if the request does not succeed.

Input contract: commentId path parameter

The path parameter commentId is a required string containing the platform comment ID to delete. Replace the {commentId} segment in /v1/comments/{commentId} with that exact ID; do not substitute a post ID, user ID, or integration ID. If the ID does not match a deletable comment for the supplied platform and account, the request will not succeed, so re-check the ID source before changing other parameters.

Input contract: platform and accountId query parameters

Both query parameters are required. The platform parameter is a required string with the exact value in "facebook" | "instagram" | "threads" | "linkedin" | "youtube" | "twitter", and accountId is a required string containing the integration ID. Send them as query parameters named exactly platform and accountId, using lowercase platform values exactly as listed. Before sending, verify that the integration identified by accountId belongs to the platform named in the request.

Worked example: DELETE request with {{API_BASE_URL}}

Build the request as DELETE with the full path /v1/comments/{commentId} and both query parameters, then add the x-access-key header. The worked example titled Delete a comment request example shows the cURL form with {{API_BASE_URL}} as the origin placeholder. After sending, inspect the HTTP status first and then the JSON body: a 200 response contains only the success field, while the other documented statuses contain success and message. Do not treat a non-200 status as a deletion, and do not retry blindly without checking whether the comment still exists.

Response body overview and failure matrix

The documented response statuses are 200, 400, 401, 402, 403, 404, 429, and 502, each with an application/json body. The 200 body is {"success": true} with success as a required boolean. Each of 400, 401, 402, 403, 404, 429, and 502 returns {"success": true, "message": "string"} with success as a required boolean and message as a required string. The table titled Response and failure matrix maps each status to its documented shape without adding semantics that the source does not state, so use the message field for diagnostics and the status code to decide your next step.

Platform-specific behavior: Twitter/X

On Twitter/X, this operation deletes your own reply tweet and costs 3 credits. Confirm the commentId is your own reply tweet before calling, and account for the credit cost in your usage planning. If the target is not your own reply tweet, do not expect this call to delete it.

Platform-specific behavior: YouTube

On YouTube, this operation removes the comment with two distinct cases. Your channel's own comments are deleted, while comments written by someone else on a video your channel owns are rejected and taken down permanently, since YouTube forbids deleting another user's comment. Check authorship before calling so you know which case applies, and treat the second case as a permanent removal rather than a reversible hide.

Platform-specific behavior: Threads, Facebook, Instagram, and LinkedIn

Deletion is not supported on Threads, because the API does not allow deleting others' replies. Do not send a Threads deletion request expecting success; instead, plan a different workflow for Threads comments. For the remaining platforms, the target differs by platform: a comment attached to a Facebook Page post, a comment attached to an Instagram Business post, and a comment attached to a LinkedIn post are each handled under their own platform value, so confirm the post type matches the platform you send.

Input contract
ParameterLocationTypeRequiredDescription / allowed values
commentIdPathstringYesPlatform comment ID to delete.
platformQuerystringYes"facebook" | "instagram" | "threads" | "linkedin" | "youtube" | "twitter"
accountIdQuerystringYesIntegration ID.

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

Response and failure matrix
StatusContent typeResponse shape
200application/json{"success": true} — success: boolean, required
400application/json{"success": true, "message": "string"} — success: boolean, required; message: string, required
401application/json{"success": true, "message": "string"} — success: boolean, required; message: string, required
402application/json{"success": true, "message": "string"} — success: boolean, required; message: string, required
403application/json{"success": true, "message": "string"} — success: boolean, required; message: string, required
404application/json{"success": true, "message": "string"} — success: boolean, required; message: string, required
429application/json{"success": true, "message": "string"} — success: boolean, required; message: string, required
502application/json{"success": true, "message": "string"} — success: boolean, required; message: string, required

Shapes exactly as documented; no invented error semantics.

Platform-specific behavior
PlatformDeletion behavior
FacebookDelete a comment on a Facebook Page post.
InstagramDelete a comment on an Instagram Business post.
LinkedInDelete a comment on a LinkedIn post.
YouTubeRemoves the comment: your channel's own comments are deleted; comments by someone else on a video your channel owns are rejected (taken down permanently).
Twitter/XDeletes your own reply tweet; costs 3 credits.
ThreadsNot supported; the API does not allow deleting others' replies.

Source-prose parity specification.

Delete a comment request example
curl -X DELETE "{{API_BASE_URL}}/v1/comments/{commentId}?platform=facebook&accountId={accountId}" \
  -H "x-access-key: <token>"
Interface fields
ScopeFieldTypeType referenceRequiredDescriptionConstraints
commentId#1commentIdstring__0YesPlatform comment ID to delete.
platform#2platformstring__0Yeskind: schemaValueIn; value: "facebook" | "instagram" | "threads" | "linkedin" | "youtube" | "twitter"
accountId#3accountIdstring__0YesIntegration ID.
response#4responseobject__0
response#4response.successboolean__1Yes
response#5responseobject__0
response#5response.successboolean__1Yes
response#5response.messagestring__2Yes