Add a Message to the News Feed log.blogpost.add

Scope: log

Who can execute the method: any user

The method log.blogpost.add adds a message to the News Feed.

Method Parameters

Required parameters are marked with *

Name `type`	Description
POST_MESSAGE* `string`	Message text
POST_TITLE `string`	Message title
DEST `array`	List of recipients who will have permission to view the message. Possible values: `SG<X>` — workgroups and projects with the identifier `X`. The identifier can be obtained using the sonet_group.get method. `U<X>` — users with the identifier `X`. The identifier can be obtained using the user.get method. `UA` — all authorized users `DR<X>` — company departments with the identifier `X`. The identifier can be obtained using the department.get method. Copied Default — `UA`
SPERM `array`	Deprecated equivalent of `DEST`
FILES `array`	Array of files in the format described in working with files. Files will be uploaded to the author's Drive and linked to the message
IMPORTANT `string`	Indicator of an important message. Possible values: `Y` — message is important `N` — message is not important Default — `N`
IMPORTANT_DATE_END `string`	Date and time in ISO 8601 format until which the message will be considered important
SITE_ID `string`	Site identifier. Default — current site
USER_ID `integer`	Identifier of the user on behalf of whom the message is published. Available only to administrators. The identifier can be obtained using the user.get method. Default — current user who initiated the method call
TAGS `string`	Message tags
BACKGROUND_CODE `string`	Background code of the message
PARSE_PREVIEW `string`	Automatic addition of a link preview from the message text. Possible values: `Y` — attempt to generate a link preview from `POST_MESSAGE` `N` — do not generate a preview Default — `N`
UF_* `mixed`	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>']`. The identifier can be obtained using the disk.storage.getchildren and disk.folder.getchildren methods. 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`	Link preview 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 — one 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 }` When creating a new survey, use a random identifier with the prefix `n`

Code Examples

How to Use Examples in Documentation

cURL (Webhook)

cURL (OAuth)

PHP

BX24.js

PHP CRest

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"POST_TITLE":"New Regulation","POST_MESSAGE":"From November 1, the approval process is updated.","DEST":["UA"],"TAGS":"regulation,approval,update","IMPORTANT":"Y","FILES":[["first-image.jpg","iVBORw0KGgoAAAANSUhEUgAAAAUA..."],["second-image.jpg","iVBORw0KGgoAAAANSUhEUgAAAAUA..."]]}' \
        https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/log.blogpost.add

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"POST_TITLE":"New Regulation","POST_MESSAGE":"From November 1, the approval process is updated.","DEST":["UA"],"TAGS":"regulation,approval,update","IMPORTANT":"Y","FILES":[["first-image.jpg","iVBORw0KGgoAAAANSUhEUgAAAAUA..."],["second-image.jpg","iVBORw0KGgoAAAANSUhEUgAAAAUA..."]],"auth":"**put_access_token_here**"}' \
        https://**put_your_bitrix24_address**/rest/log.blogpost.add

try
        {
            const response = await $b24.callMethod(
                'log.blogpost.add',
                {
                    POST_TITLE: 'New Regulation',
                    POST_MESSAGE: 'From November 1, the approval process is updated.',
                    DEST: ['UA'],
                    TAGS: 'regulation,approval,update',
                    IMPORTANT: 'Y',
                    FILES: [
                        ['first-image.jpg', 'iVBORw0KGgoAAAANSUhEUgAAAAUA...'],
                        ['second-image.jpg', 'iVBORw0KGgoAAAANSUhEUgAAAAUA...']
                    ]
                }
            );
            
            const result = response.getData().result;
            console.log('Created element with ID:', result);
            processResult(result);
        }
        catch( error )
        {
            console.error('Error:', error);
        }

try {
            $response = $b24Service
                ->core
                ->call(
                    'log.blogpost.add',
                    [
                        'POST_TITLE' => 'New Regulation',
                        'POST_MESSAGE' => 'From November 1, the approval process is updated.',
                        'DEST' => ['UA'],
                        'TAGS' => 'regulation,approval,update',
                        'IMPORTANT' => 'Y',
                        'FILES' => [
                            ['first-image.jpg', 'iVBORw0KGgoAAAANSUhEUgAAAAUA...'],
                            ['second-image.jpg', 'iVBORw0KGgoAAAANSUhEUgAAAAUA...']
                        ]
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            echo 'Success: ' . print_r($result, true);
            processData($result);
        
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error adding blog post: ' . $e->getMessage();
        }

BX24.callMethod(
            'log.blogpost.add',
            {
                POST_TITLE: 'New Regulation',
                POST_MESSAGE: 'From November 1, the approval process is updated.',
                DEST: ['UA'],
                TAGS: 'regulation,approval,update',
                IMPORTANT: 'Y',
                FILES: [
                    ['first-image.jpg', 'iVBORw0KGgoAAAANSUhEUgAAAAUA...'],
                    ['second-image.jpg', 'iVBORw0KGgoAAAANSUhEUgAAAAUA...']
                ]
            },
            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.add',
            [
                'POST_TITLE' => 'New Regulation',
                'POST_MESSAGE' => 'From November 1, the approval process is updated.',
                'DEST' => ['UA'],
                'TAGS' => 'regulation,approval,update',
                'IMPORTANT' => 'Y',
                'FILES' => [
                    ['first-image.jpg', 'iVBORw0KGgoAAAANSUhEUgAAAAUA...'],
                    ['second-image.jpg', 'iVBORw0KGgoAAAANSUhEUgAAAAUA...']
                ]
            ]
        );
        
        echo '<PRE>';
        print_r($result);
        echo '</PRE>';

Response Handling

HTTP Status: 200

{
            "result": 217,
            "time": {
                "start": 1773750554,
                "finish": 1773750555.955794,
                "duration": 1.955794095993042,
                "processing": 1,
                "date_start": "2026-03-17T15:29:14+01:00",
                "date_finish": "2026-03-17T15:29:15+01:00",
                "operating_reset_at": 1773751154,
                "operating": 0.9908020496368408
            }
        }

Returned Data

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

Error Handling

HTTP Status: 400

{
            "error": "SONET_CONTROLLER_LIVEFEED_BLOGPOST_ADD_ERROR",
            "error_description": "Blog post hasn't been added"
        }

Name `type`	Description
error `string`	String error code. It may consist of digits, Latin letters, and underscores
error_description `error_description`	Textual description of the error. The description is not intended to be shown to the end user in its raw form

Possible Error Codes

Code	Description	Value
`SONET_CONTROLLER_LIVEFEED_BLOGPOST_ADD_ERROR`	`Blog post hasn't been added`	General error saving the message, for example, when `POST_MESSAGE` is empty
`SONET_CONTROLLER_LIVEFEED_BLOGPOST_ADD_ERROR`	`No destination specified`	Failed to determine the message recipients
`SONET_CONTROLLER_LIVEFEED_BLOGPOST_MODULE_BLOG_NOT_INSTALLED`	`Blog module is not installed`	The `blog` module is not installed
`SONET_CONTROLLER_LIVEFEED_BLOG_NOT_FOUND`	`Blog not found`	Failed to retrieve the blog to which the message belongs
—	`Cannot add blog post`	Internal error when creating the message

Statuses and System Error Codes

HTTP Status: 20x, 40x, 50x

The errors described below may occur when calling any method.

Status	Code Error Message	Description
`500`	`INTERNAL_SERVER_ERROR` Internal server error	An internal server error has occurred, please contact the server administrator or Bitrix24 technical support
`500`	`ERROR_UNEXPECTED_ANSWER` Server returned an unexpected response	An internal server error has occurred, please contact the server administrator or Bitrix24 technical support
`503`	`QUERY_LIMIT_EXCEEDED` Too many requests	The request intensity limit has been exceeded
`405`	`ERROR_BATCH_METHOD_NOT_ALLOWED` Method is not allowed for batch usage	The current method is not allowed to be called using batch
`400`	`ERROR_BATCH_LENGTH_EXCEEDED` Max batch length exceeded	The maximum length of parameters passed to the batch method has been exceeded
`401`	`NO_AUTH_FOUND` Wrong authorization data	Invalid access token or webhook code
`400`	`INVALID_REQUEST` Https required	The methods must be called using the HTTPS protocol
`503`	`OVERLOAD_LIMIT` REST API is blocked due to overload	The REST API is blocked due to overload. This is a manual individual block, to remove it you need to contact Bitrix24 technical support
`403`	`ACCESS_DENIED` REST API is available only on commercial plans	The REST API is available only on commercial plans
`403`	`INVALID_CREDENTIALS` Invalid request credentials	The user whose access token or webhook was used to call the method lacks permissions
`404`	`ERROR_MANIFEST_IS_NOT_AVAILABLE` Manifest is not available	The manifest is not available
`403`	`insufficient_scope` The request requires higher privileges than provided by the webhook token	The request requires higher privileges than those provided by the webhook token
`401`	`expired_token` The access token provided has expired	The provided access token has expired
`403`	`user_access_error` The user does not have access to the application	The user does not have access to the application. This means that the application is installed, but the account administrator has allowed access to this application only for specific users
`500`	`PORTAL_DELETED` Portal was deleted	The public part of the site is closed. To open the public part of the site on an on-premise installation, disable the option "Temporary closure of the public part of the site". Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site

Continue Learning

Overview of Methods

Edit Message

Add a Message to the News Feed log.blogpost.add

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