Update News Feed Message log.blogpost.update

{% note tip "" %}

If you are developing integrations for Bitrix24 using AI tools (Codex, Claude Code, Cursor), connect to the MCP server so that the assistant can utilize the official REST documentation.

{% endnote %}

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

{% include Note on required parameters %}

#| || 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.

{% note info "" %}

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.

{% endnote %} || || 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 {#uf-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.

{% note info "" %}

When specifying FILES, the UF_BLOG_POST_FILE parameter is ignored.

{% endnote %} || || 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

{% include Footnote on examples %}

{% list tabs %}

cURL (Webhook)

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 (OAuth)

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

JS (TS)

// 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)
}

JS (UMD)

<!-- 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>

PHP

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.js

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());
        }
    }
);

PHP CRest

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)

{% endlist %}

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."
}

{% include notitle Error Handling %}

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. || |#

{% include System Errors %}

Navigation Menu

Uh oh!

Update News Feed Message log.blogpost.update

Method Parameters

Custom Fields {#uf-fields}

Code Examples

Response Handling

Returned Data

Error Handling

Possible Error Codes

Continue Learning

Uh oh!

FilesExpand file tree

log-blogpost-update.md

Latest commit

History

log-blogpost-update.md

File metadata and controls

Update News Feed Message log.blogpost.update

Method Parameters

Custom Fields {#uf-fields}

Code Examples

Response Handling

Returned Data

Error Handling

Possible Error Codes

Continue Learning