Add Recipients to News Feed Message log.blogpost.share

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.

Scope: log

Who can execute the method: administrator or message author

The method log.blogpost.share adds new recipients to a news feed message.

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
DEST* `array`	List of new recipients who will be granted access 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
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.

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_ID":217,"DEST":["SG69","DR4"]}' \
        https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/log.blogpost.share

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"POST_ID":217,"DEST":["SG69","DR4"],"auth":"**put_access_token_here**"}' \
        https://**put_your_bitrix24_address**/rest/log.blogpost.share

try
        {
            const response = await $b24.callMethod(
                'log.blogpost.share',
                {
                    POST_ID: 217,
                    DEST: ['SG69', 'DR4'],
                }
            );
            
            const result = response.getData().result;
            console.log(result);
            
            processResult(result);
        }
        catch( error )
        {
            console.error('Error:', error);
        }

try {
            $response = $b24Service
                ->core
                ->call(
                    'log.blogpost.share',
                    [
                        'POST_ID' => 217,
                        'DEST' => ['SG69', 'DR4']
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            echo 'Success: ' . print_r($result, true);
            processData($result);
        
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error sharing blog post: ' . $e->getMessage();
        }

BX24.callMethod(
            'log.blogpost.share',
            {
                POST_ID: 217,
                DEST: ['SG69', 'DR4']
            },
            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.share',
            [
                'POST_ID' => 217,
                'DEST' => ['SG69', 'DR4']
            ]
        );
        
        echo '<PRE>';
        print_r($result);
        echo '</PRE>';

Response Handling

HTTP Status: 200

{
            "result": true,
            "time": {
                "start": 1773814878,
                "finish": 1773814878.602921,
                "duration": 0.6029210090637207,
                "processing": 0,
                "date_start": "2026-03-18T09:21:18+02:00",
                "date_finish": "2026-03-18T09:21:18+02:00",
                "operating_reset_at": 1773815478,
                "operating": 0.284437894821167
            }
        }

Returned Data

Name `type`	Description
result `boolean`	`true` if recipients were added
time `time`	Information about the request execution time

Error Handling

HTTP Status: 400

{
            "error": "",
            "error_description": "Wrong destinations"
        }

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
—	`Wrong post ID`	Invalid `POST_ID`
—	`Blog module not installed`	`blog` module is not installed
—	`Wrong destinations`	Invalid list of recipients `DEST`
—	`No read perms`	Insufficient permissions to read the message
—	No access to one or more message recipients	No permissions for one or more recipients from `DEST`

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 permitted for calls 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 HTTPS protocol is required for method calls
`503`	`OVERLOAD_LIMIT` REST API is blocked due to overload	The REST API is blocked due to overload. This is a manual individual block; please contact Bitrix24 technical support to lift it
`403`	`ACCESS_DENIED` REST API is available only on commercial plans	The REST API is only available on commercial plans
`403`	`INVALID_CREDENTIALS` Invalid request credentials	The user associated with the access token or webhook used to call the method lacks the necessary 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 portal administrator has restricted access to this application to specific users only
`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 "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

Delete Message

View Users Who Read Important Message

Add Recipients to News Feed Message log.blogpost.share

Method ParametersMethod Parameters

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