لوكلاء AI: ملف markdown لهذه الصفحة — /docs-content-en/feed-comments.md فهرس التوثيق — /llms.txt
مقالات التوثيق متاحة حاليًا باللغة الإنجليزية فقط.
Feed comments
Deleting comments from the Bitrix24 Feed by their feed ID. This ID differs from the post comment ID and is taken from the response of the method that reads the user's comments.
Scope: log | Base URL: https://vibecode.bitrix24.com/v1 | Authorization: X-Api-Key
Which ID to use
The GET /v1/posts/comments method returns two identifiers for each comment. Each delete method accepts only its own.
| Response field | What it is | Delete method |
|---|---|---|
Response fieldid |
What it isComment ID in the feed | Delete methodDELETE /v1/feed-comments/:id |
Response fieldcommentId + postId |
What it isPost comment ID and post ID | Delete methodDELETE /v1/posts/:id/comments/:commentId |
Deleting by the feed ID removes the comment from the feed, but the post comment remains and the post's comment counter numComments does not decrease. To delete a post comment, use DELETE /v1/posts/:id/comments/:commentId.
Quick start
Delete a feed comment with a known ID:
curl -X DELETE https://vibecode.bitrix24.com/v1/feed-comments/6195 \
-H "X-Api-Key: YOUR_API_KEY"
Response:
{
"success": true,
"data": {
"deleted": true
}
}
Full example
Find a comment on post 315 in the feed and delete it. The read method does not filter by post, so the comment is selected by the postId field on the client side.
BASE='https://vibecode.bitrix24.com/v1'
# 1. User comments → feed ID of the first comment on post 315
FEED_ID=$(curl -s "$BASE/posts/comments?limit=100" \
-H "X-Api-Key: YOUR_API_KEY" \
| jq -r '[.data.comments[] | select(.postId == 315)][0].id')
# 2. Delete the comment from the feed
curl -s -X DELETE "$BASE/feed-comments/$FEED_ID" \
-H "X-Api-Key: YOUR_API_KEY"
# 3. Check: the feed no longer has a comment with this ID
curl -s "$BASE/posts/comments?limit=100" \
-H "X-Api-Key: YOUR_API_KEY" \
| jq --argjson id "$FEED_ID" '[.data.comments[] | select(.id == $id)] | length'
Step 1 returns a response in which the comment has both identifiers — id for deleting from the feed and commentId for deleting the post comment:
{
"success": true,
"data": {
"comments": [
{
"id": 6195,
"commentId": 53,
"postId": 315,
"date": "2026-10-20T12:50:19+00:00",
"text": "Comment for the deletion check",
"attach": []
}
],
"files": []
}
}
Step 2 returns {"success": true, "data": {"deleted": true}}, step 3 prints 0. Deleting the same ID again returns 404 ENTITY_NOT_FOUND.
Endpoint reference
| Method | Path | Bitrix24 method | Description |
|---|---|---|---|
| MethodDELETE | Path/v1/feed-comments/:id |
Bitrix24 methodlog.comment.delete | DescriptionDelete a feed comment |
Error codes
Feed comment errors
| HTTP | Code | When |
|---|---|---|
| HTTP400 | CodeINVALID_PARAMS |
Whenid in the path is not a positive integer |
| HTTP404 | CodeENTITY_NOT_FOUND |
WhenThe feed has no comment with this id, including after a repeated deletion |
| HTTP403 | CodeBITRIX_ACCESS_DENIED |
WhenThe key's user has no permission to delete this comment |
| HTTP422 | CodeBITRIX_ERROR |
WhenBitrix24 did not confirm the deletion or rejected the request |
System errors
| HTTP | Code | When |
|---|---|---|
| HTTP401 | CodeMISSING_API_KEY |
WhenThe X-Api-Key header is missing |
| HTTP401 | CodeINVALID_API_KEY |
WhenThe key is not found or has been revoked |
| HTTP401 | CodeTOKEN_MISSING |
WhenThe key has no portal tokens. An OAuth application key requires the Authorization: Bearer header |
| HTTP403 | CodeSCOPE_DENIED |
WhenThe key does not have the log scope |
| HTTP403 | CodeWRITE_BLOCKED_READONLY_KEY |
WhenThe key works in read-only mode |
| HTTP429 | CodeRATE_LIMITED |
WhenThe request rate to Bitrix24 was exceeded |
| HTTP502 | CodeBITRIX_UNAVAILABLE |
WhenBitrix24 is unavailable |
| HTTP503 | CodeBITRIX_TIMEOUT |
WhenBitrix24 accepted the request but did not respond in time |
Full list of common API errors — Errors.