Update News Feed Message log.blogpost.update

Choose a tool for developing with an AI agent:

use Alaio Vibecode to build an app for Bitrix24 from a task description without knowing any programming language. The agent writes the code and deploys the app to a server, with no manual hosting setup
use the MCP server to develop a REST API integration in your own project. The agent refers to the official REST documentation

Scope: log

Who can execute the method: administrator or message author

The method log.blogpost.update updates a message in the News Feed.

Method Parameters

Required parameters are marked with *

Name `type`	Description
POST_ID* `integer`	Identifier of the message. You can obtain the identifier using the log.blogpost.get method.
POST_MESSAGE `string`	New text of the message.
POST_TITLE `string`	New title of the message. If neither `POST_TITLE` nor `POST_MESSAGE` is provided, the method will return an error `EMPTY_TITLE`. If only `POST_MESSAGE` is provided, the title from the original message will not be retained.
DEST `array`	New list of recipients who will have the right to view the message. Possible values: `SG<X>` — workgroups and projects with the identifier `X`. You can retrieve the identifier using the sonet_group.get method `U<X>` — users with the identifier `X`. You can retrieve the identifier using the user.get method `UA` — all authorized users `DR<X>` — company departments with the identifier `X`. You can retrieve the identifier using the department.get method
SPERM `array`	Deprecated equivalent of `DEST`.
FILES `array`	Array of files in the format described in working with files. To delete a file, use the format `{ ID: 'del' }`, where `ID` is the identifier of the file attachment in the message. You can obtain the identifier using the log.blogpost.get method.
IMPORTANT `string`	Indicator of an important message. Possible values: `Y` — message is important `N` — message is not important
IMPORTANT_DATE_END `string`	Date and time in ISO 8601 format until which the message will be considered important.
SITE_ID `string`	Identifier of the site.
USER_ID `integer`	Identifier of the user on behalf of whom the message is edited. Available only to administrators. The identifier can be obtained using the user.get method. By default, it is the current user who initiated the method call.
UF_* `any`	Custom fields. A specific set of fields is supported, depending on the account settings.

Custom Fields

Name `type`	Description
UF_BLOG_POST_FILE `array`	Alternative to `FILES`. Pass a list of Drive file identifiers in the format `['n<ID_drive_file>']`. You can obtain the identifier using the disk.storage.getchildren and disk.folder.getchildren methods. To clear the list of files from the message, pass `['empty']`. The files will not be physically deleted from the Drive; only the attachment to the message will be removed. When specifying `FILES`, the `UF_BLOG_POST_FILE` parameter is ignored.
UF_BLOG_POST_IMPRTNT `integer`	Indicator of an important message. Automatically filled when `IMPORTANT = 'Y'`.
UF_IMPRTANT_DATE_END `datetime`	Expiration date of the important message. Automatically filled when `IMPORTANT_DATE_END` is provided.
UF_BLOG_POST_URL_PRV `integer`	Preview link from the message text. Automatically filled when `PARSE_PREVIEW = 'Y'`, if the preview was successfully generated.
UF_GRATITUDE `integer`	Data for the Gratitude functionality in the format: `GRATITUDE_MEDAL: '<XML_ID_medal>', GRATITUDE_EMPLOYEES: [<user_ID>]`
UF_BLOG_POST_VOTE `integer`	Survey data in the format: `UF_BLOG_POST_VOTE: 'n<ID_survey>', 'UF_BLOG_POST_VOTE_n<ID_survey>_DATA': { QUESTIONS: [ { QUESTION: 'Question', FIELD_TYPE: 0, // Selection type: 0 — single option, 1 — multiple options ANSWERS: [ { MESSAGE: 'Answer 1' }, { MESSAGE: 'Answer 2' } ] } ], ANONYMITY: 0, // Voting anonymity: 0 — no, 1 — yes OPTIONS: 0 // Re-voting: 0 — prohibited, 1 — allowed }` You can obtain the identifier of an existing survey using the log.blogpost.get method.

Code Examples

How to Use Examples in Documentation

cURL (Webhook)

cURL (OAuth)

JS (TS)

JS (UMD)

Python

PHP

BX24.js

PHP CRest

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"POST_ID":217,"POST_TITLE":"New Message Title","FILES":{"505":"del"}}' \
        https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/log.blogpost.update

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"POST_ID":217,"POST_TITLE":"New Message Title","FILES":{"505":"del"},"auth":"**put_access_token_here**"}' \
        https://**put_your_bitrix24_address**/rest/log.blogpost.update

// This snippet is an ES module: top-level await requires type="module" or a bundler.
        // $b24 is an already-initialized SDK instance (see the SDK "Get started" guide).
        import { Text } from '@bitrix24/b24jssdk'
        import type { B24Frame } from '@bitrix24/b24jssdk'
        
        declare const $b24: B24Frame
        
        try {
          const response = await $b24.actions.v2.call.make<number>({
            method: 'log.blogpost.update',
            params: {
              POST_ID: 217,
              POST_TITLE: 'New post title',
              FILES: {
                505: 'del',
              },
            },
            requestId: Text.getUuidRfc4122()
          })
        
          // The payload is available only on a successful response
          if (!response.isSuccess) {
            console.error(response.getErrorMessages().join('; '))
          } else {
            const result = response.getData()!.result
            console.info('Updated post ID:', result)
          }
        } catch (error) {
          // Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
          console.error(error)
        }

<!-- Load the SDK (UMD build); it is exposed as the global B24Js -->
        <script src="https://unpkg.com/@bitrix24/b24jssdk@1/dist/umd/index.min.js"></script>
        <script>
          async function updateBlogPost() {
            try {
              // Initialize the SDK inside a Bitrix24 frame
              const $b24 = await B24Js.initializeB24Frame()
        
              const response = await $b24.actions.v2.call.make({
                method: 'log.blogpost.update',
                params: {
                  POST_ID: 217,
                  POST_TITLE: 'New post title',
                  FILES: {
                    505: 'del',
                  },
                },
                requestId: B24Js.Text.getUuidRfc4122()
              })
        
              // The payload is available only on a successful response
              if (!response.isSuccess) {
                console.error(response.getErrorMessages().join('; '))
                return
              }
        
              const result = response.getData().result
              console.info('Updated post ID:', result)
            } catch (error) {
              // Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
              console.error(error)
            }
          }
        
          document.addEventListener('DOMContentLoaded', updateBlogPost)
        </script>

from b24pysdk.errors import BitrixAPIError, BitrixSDKException
        
        try:
            bitrix_response = client.log.blogpost.update(
                post_id=217,
                post_title="New post title",
                files={
                    505: "del",
                },
            ).response
            result = bitrix_response.result
            print(result)
        except BitrixAPIError as error:
            print(
                "Bitrix API error",
                f"error: {error.error}",
                f"error_description: {error.error_description}",
                sep="\n",
            )
        except BitrixSDKException as error:
            print(f"Bitrix SDK error: {error.message}")
        except Exception as error:
            print(f"Unexpected error: {error}")

try {
            $response = $b24Service
                ->core
                ->call(
                    'log.blogpost.update',
                    [
                        'POST_ID' => 217,
                        'POST_TITLE' => 'New Message Title',
                        'FILES' => [
                            505 => 'del'
                        ]
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            echo 'Success: ' . print_r($result, true);
            processData($result);
        
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error updating blog post: ' . $e->getMessage();
        }

BX24.callMethod(
            'log.blogpost.update',
            {
                POST_ID: 217,
                POST_TITLE: 'New Message Title',
                FILES: {
                    505: 'del'
                }
            },
            function(result)
            {
                if (result.error())
                {
                    console.error(result.error(), result.error_description());
                }
                else
                {
                    console.log(result.data());
                }
            }
        );

require_once('crest.php');
        
        $result = CRest::call(
            'log.blogpost.update',
            [
                'POST_ID' => 217,
                'POST_TITLE' => 'New Message Title',
                'FILES' => [
                    505 => 'del'
                ]
            ]
        );
        
        echo '<PRE>';
        print_r($result);
        echo '</PRE>';

// client and ctx are already created — see the Go SDK section
        res, err := client.Core().Call(ctx, "log.blogpost.update", b24.Params{
        	"POST_ID":    217,
        	"POST_TITLE": "New Message Title",
        	"FILES": b24.Params{
        		"505": "del",
        	},
        })
        if err != nil {
        	return fmt.Errorf("log.blogpost.update: %w", err)
        }
        
        var value b24.ID
        if err := json.Unmarshal(res.Result, &value); err != nil {
        	return fmt.Errorf("parse response: %w", err)
        }
        fmt.Println("result:", value)

Response Handling

HTTP Status: 200

{
            "result": 217,
            "time": {
                "start": 1773817731,
                "finish": 1773817731.902982,
                "duration": 0.9029819965362549,
                "processing": 0,
                "date_start": "2026-03-18T10:08:51+01:00",
                "date_finish": "2026-03-18T10:08:51+01:00",
                "operating_reset_at": 1773818331,
                "operating": 0.704833984375
            }
        }

Returned Data

Name `type`	Description
result `integer`	Identifier of the updated message.
time `time`	Information about the request execution time.

Error Handling

HTTP Status: 400

{
            "error": "EMPTY_TITLE",
            "error_description": "Message title is not specified."
        }

Name `type`	Description
error `string`	String error code. It consists of digits, Latin letters, and underscores. It may arrive empty — in that case only `error_description` shows the reason
error_description `string`	Error message for the developer. Do not show it to the end user without processing

Possible Error Codes

Code	Description	Value
`SONET_CONTROLLER_LIVEFEED_BLOGPOST_UPDATE_ERROR`	`Wrong post ID`	Invalid `POST_ID`.
`EMPTY_TITLE`	`Message title is not specified.`	Neither `POST_TITLE` nor `POST_MESSAGE` is specified.
`SONET_CONTROLLER_LIVEFEED_BLOGPOST_UPDATE_ERROR`	`Blog module is not installed.`	The `blog` module is not installed.
`SONET_CONTROLLER_LIVEFEED_BLOGPOST_UPDATE_ERROR`	`No write perms`	Insufficient permissions to modify the message.
`SONET_CONTROLLER_LIVEFEED_BLOGPOST_UPDATE_ERROR`	`No post found`	Message not found.
`SONET_CONTROLLER_LIVEFEED_BLOGPOST_UPDATE_ERROR`	`No blog found`	Unable to retrieve the author's blog.
—	`Cannot update blog post`	Internal error while updating the message.

Statuses and System Error Codes

HTTP Status: 4xx, 5xx

The errors described below are returned by the REST API itself, not by the logic of a specific method. They can arrive in response to any method.

Status	Code Error Message	Description
`500`	`INTERNAL_SERVER_ERROR` Internal server error	An internal server error has occurred. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support
`500`	`ERROR_UNEXPECTED_ANSWER` Server returned an unexpected response	The server returned an unexpected response. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support
`503`	`QUERY_LIMIT_EXCEEDED` Too many requests	The request intensity limit has been exceeded
`429`	`OPERATION_TIME_LIMIT` Method is blocked due to operation time limit	The method is blocked because the request resource intensity limit has been exceeded. The block is lifted automatically once the accumulated execution time of the method no longer exceeds the limit
`401`	`NO_AUTH_FOUND` Wrong authorization data	The request contains no authorization data: neither an access token nor a webhook code was passed
`401`	`INVALID_REQUEST` Https required	Methods are called over the HTTPS protocol only
`401`	`OVERLOAD_LIMIT` REST API is blocked due to overload	The REST API is blocked due to overload. This is a manual individual block. To have it lifted, contact Bitrix24 technical support
`401`	`ACCESS_DENIED` REST is available only on commercial plans	REST API access is not active for this account. In Bitrix24 Cloud, check the current plan or trial status: Vibe+ plans include REST API access, while Essentials plans do not. A webhook receives a different error message — `REST is available only by subscription`
`401`	`INVALID_CREDENTIALS` Invalid request credentials	No active webhook with the specified user identifier and secret code was found
`404`	`ERROR_METHOD_NOT_FOUND` Method not found!	No method with this name was found. The name is misspelled, the method does not exist in the REST API, or it is unavailable without the required scope
`401`	`insufficient_scope` The request requires higher privileges than provided by the webhook token	The request requires broader permissions than the token has: for a webhook these are the permissions granted to it, for an application it is the scope. For an application, the error message ends with `provided by the access token`
`401`	`expired_token` The access token provided has expired	The access token has expired
`401`	`user_access_error` The user does not have access to the application	The application is installed, but the Bitrix24 administrator has granted access to it only to specific users
`403`	`PORTAL_DELETED` Portal was deleted	The public part of the site is closed. To open it on an on-premise installation, disable the "Temporary closure of the public part of the site" option. Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site

Continue Learning

Was the article helpful?

Add Message

Get List of Messages

Update News Feed Message log.blogpost.update

Method ParametersMethod Parameters

Custom FieldsCustom Fields

Code ExamplesCode Examples

Response HandlingResponse Handling

Returned DataReturned Data

Error HandlingError Handling

Possible Error CodesPossible Error Codes

Statuses and System Error CodesStatuses and System Error Codes

Continue LearningContinue Learning