Move an Activity Binding v 3.0 crm.activity.binding.move

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: crm

Who can execute the method: a user with permission to edit the activity and both CRM items

This method belongs to REST 3.0. The call specifics and response format of the new API version are described in the REST 3.0 overview.

The crm.activity.binding.move method moves an activity binding from one CRM item to another and returns the activity bindings after the move. This way you can change the item of an activity with a single binding, which cannot be removed with the crm.activity.binding.unbind method.

Method Parameters

Required parameters are marked with *

Name
type

Description

activityId*
integer

Activity ID.

The ID can be retrieved with the crm.<type>.activity.list method

from*
object

CRM item in the {"entityTypeId": 2, "entityId": 9001} format: entityTypeId is the object type ID, entityId is the item ID. The item the activity is unbound from. The activity must be bound to it.

Object type IDs are returned by the crm.dictionary.entitytype.list method, and for an SPA by crm.type.list

to*
object

CRM item the activity is bound to, in the same format

Code Examples

How to Use Examples in Documentation

The new API call differs by adding the /api/ segment to the request URL:

https://{installation_address}/rest/api/{user_id}/{webhook_token}/crm.activity.binding.move

The examples move the activity from the item of SPA 1038 with the ID 41 to the deal 9001.

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"activityId":8463,"from":{"entityTypeId":1038,"entityId":41},"to":{"entityTypeId":2,"entityId":9001}}' \
        https://**put_your_bitrix24_address**/rest/api/**put_your_user_id_here**/**put_your_webhook_here**/crm.activity.binding.move
        
curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"activityId":8463,"from":{"entityTypeId":1038,"entityId":41},"to":{"entityTypeId":2,"entityId":9001},"auth":"**put_access_token_here**"}' \
        https://**put_your_bitrix24_address**/rest/api/crm.activity.binding.move
        

CRM methods are not yet included in the list of REST 3.0 methods known to $b24.actions.v3.call.make: such a call returns the SDK error JSSDK_CORE_METHOD_NOT_SUPPORT_IN_API_V3. Call the method through the REST 3.0 HTTP client — $b24.getHttpClient(ApiVersion.v3).call.

import { ApiVersion, Text } from '@bitrix24/b24jssdk'
        import type { B24Frame } from '@bitrix24/b24jssdk'
        
        declare const $b24: B24Frame
        
        type ActivityMoveResult = {
          items: Array<{
            entityTypeId: number
            entityId: number
          }>
        }
        
        try {
          const response = await $b24.getHttpClient(ApiVersion.v3).call<ActivityMoveResult>(
            'crm.activity.binding.move',
            {
              activityId: 8463,
              from: {
                entityTypeId: 1038,
                entityId: 41,
              },
              to: {
                entityTypeId: 2,
                entityId: 9001,
              },
            },
            Text.getUuidRfc4122()
          )
        
          if (!response.isSuccess) {
            console.error(response.getErrorMessages().join('; '))
          } else {
            const result = response.getData()!.result
            console.info('Bindings:', result.items)
          }
        } catch (error) {
          // Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
          console.error(error)
        }
        

CRM methods are not yet included in the list of REST 3.0 methods known to $b24.actions.v3.call.make. Call the method through the REST 3.0 HTTP client — $b24.getHttpClient(B24Js.ApiVersion.v3).call.

<script src="https://unpkg.com/@bitrix24/b24jssdk@1/dist/umd/index.min.js"></script>
        <script>
          async function moveActivity() {
            try {
              const $b24 = await B24Js.initializeB24Frame()
        
              const response = await $b24.getHttpClient(B24Js.ApiVersion.v3).call(
                'crm.activity.binding.move',
                {
                  activityId: 8463,
                  from: {
                    entityTypeId: 1038,
                    entityId: 41,
                  },
                  to: {
                    entityTypeId: 2,
                    entityId: 9001,
                  },
                },
                B24Js.Text.getUuidRfc4122()
              )
        
              if (!response.isSuccess) {
                console.error(response.getErrorMessages().join('; '))
                return
              }
        
              const result = response.getData().result
              console.info('Bindings:', result.items)
            } catch (error) {
              // Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
              console.error(error)
            }
          }
        
          document.addEventListener('DOMContentLoaded', moveActivity)
        </script>
        

b24pysdk has no ready-made wrappers for CRM methods, and the SDK sends to REST 3.0 only the methods from the Config().api_v3_methods list. Add the method to this list and call it via bitrix_token.call_method with prefer_version=3.

from b24pysdk import Config
        from b24pysdk.errors import BitrixSDKException
        from b24pysdk.errors.v3 import BitrixAPIError
        
        method = "crm.activity.binding.move"
        Config().configure(api_v3_methods=Config().api_v3_methods | {method})
        
        try:
            response = bitrix_token.call_method(
                api_method=method,
                params={
                    "activityId": 8463,
                    "from": {
                        "entityTypeId": 1038,
                        "entityId": 41,
                    },
                    "to": {
                        "entityTypeId": 2,
                        "entityId": 9001,
                    },
                },
                prefer_version=3,
            )
            result = response["result"]
            print(result)
        except BitrixAPIError as error:
            print(
                "Bitrix API error",
                f"code: {error.code}",
                f"message: {error.error.message}",
                sep="\n",
            )
        except BitrixSDKException as error:
            print(f"Bitrix SDK error: {error.message}")
        except Exception as error:
            print(f"Unexpected error: {error}")
        

SDKs do not yet support the /rest/api/ address in calls. Use direct HTTP requests, for example, via curl or fetch.

try {
            $response = $b24Service
                ->core
                ->call(
                    'crm.activity.binding.move',
                    [
                        'activityId' => 8463,
                        'from' => [
                            'entityTypeId' => 1038,
                            'entityId' => 41,
                        ],
                        'to' => [
                            'entityTypeId' => 2,
                            'entityId' => 9001,
                        ],
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            print_r($result);
        } catch (Throwable $e) {
            echo $e->getMessage();
        }
        

SDKs do not yet support the /rest/api/ address in calls. Use direct HTTP requests, for example, via curl or fetch.

BX24.callMethod(
            'crm.activity.binding.move',
            {
                activityId: 8463,
                from: {
                    entityTypeId: 1038,
                    entityId: 41,
                },
                to: {
                    entityTypeId: 2,
                    entityId: 9001,
                },
            },
            result => {
                if (result.error())
                    console.error(result.error());
                else
                    console.dir(result.data());
            }
        );
        

SDKs do not yet support the /rest/api/ address in calls. Use direct HTTP requests, for example, via curl or fetch.

require_once('crest.php');
        
        $result = CRest::call(
            'crm.activity.binding.move',
            [
                'activityId' => 8463,
                'from' => [
                    'entityTypeId' => 1038,
                    'entityId' => 41,
                ],
                'to' => [
                    'entityTypeId' => 2,
                    'entityId' => 9001,
                ],
            ]
        );
        
        echo '<PRE>';
        print_r($result);
        echo '</PRE>';
        
// client and ctx are already created — see the Go SDK section
        res, err := client.Core().Call(ctx, "crm.activity.binding.move", b24.Params{
        	"activityId": 8463,
        	"from": b24.Params{
        		"entityTypeId": 1038,
        		"entityId":     41,
        	},
        	"to": b24.Params{
        		"entityTypeId": 2,
        		"entityId":     9001,
        	},
        })
        if err != nil {
        	return fmt.Errorf("crm.activity.binding.move: %w", err)
        }
        
        var result struct {
        	Items []struct {
        		EntityTypeID int `json:"entityTypeId"`
        		EntityID     int `json:"entityId"`
        	} `json:"items"`
        }
        if err := json.Unmarshal(res.Result, &result); err != nil {
        	return fmt.Errorf("parse response: %w", err)
        }
        for _, item := range result.Items {
        	fmt.Println(item.EntityTypeID, item.EntityID)
        }
        

Response Handling

HTTP status: 200

{
            "result": {
                "items": [
                    {
                        "entityTypeId": 2,
                        "entityId": 9001
                    }
                ]
            },
            "time": {
                "start": 1793711360,
                "finish": 1793711360.764732,
                "duration": 0.7647318840026855,
                "processing": 0,
                "date_start": "2026-11-03T16:09:20+03:00",
                "date_finish": "2026-11-03T16:09:20+03:00",
                "operating_reset_at": 1793711940,
                "operating": 0
            }
        }
        

Returned Data

Name
type

Description

result
object

Object with response data

result.items
object[]

Activity bindings after the operation: entityTypeId is the object type, entityId is the item ID. Bindings to items you cannot view are not included in the response but are retained

time
time

Information about the request execution time

Error Handling

HTTP status: 400

{
            "error": {
                "code": "CRM_ACTIVITY_BINDING_NOT_FOUND",
                "message": "The activity is not associated with the specified CRM item."
            }
        }
        

Name
type

Description

error.code
string

String error code. Use it to identify the type of exception

error.message
string

Text description of the error

error.validation
array

Array with error details. Present only in data validation errors BITRIX_REST_V3_EXCEPTION_VALIDATION_REQUESTVALIDATIONEXCEPTION

error.validation[].field
string

Name of the field where the validation error occurred

error.validation[].message
string

Description of the error related to the specified field

Possible Error Codes

Request Validation Errors

Error Code: BITRIX_REST_V3_EXCEPTION_VALIDATION_REQUESTVALIDATIONEXCEPTION

Field

Error description

How to Fix

activityId

Required field activityId is missing

Pass activityId

activityId

Field value must be 1 or greater

Pass a positive activity ID

from

Required field from is missing

Pass from as an object

from

The parent must be an object of entityTypeId and entityId.

Pass from as an object with the entityTypeId and entityId fields, not as an array

from.entityId

Required field from.entityId is missing

Pass both fields: entityTypeId and entityId

from.entityTypeId

This request requires data type integer in field from.entityTypeId

Pass the IDs as numbers, not strings

from.entityTypeId

The type of the parent is not defined.

Pass an existing object type ID

from.entityId

The identifier of the parent must be positive.

Pass a positive item ID

to

Required field to is missing

Pass to as an object. The same checks apply to to as to from

Binding Not Found

Error Code: CRM_ACTIVITY_BINDING_NOT_FOUND

Field

Error description

How to Fix

-

The activity is not associated with the specified CRM item

Check from with the crm.activity.binding.list method

Activity Not Found

Error Code: BITRIX_REST_V3_EXCEPTION_ENTITYNOTFOUNDEXCEPTION

Field

Error description

How to Fix

-

Entity with ID #ID# was not found

The activity does not exist or you have no permission to edit it. Check activityId

Access Denied

Error Code: BITRIX_REST_V3_EXCEPTION_ACCESSDENIEDEXCEPTION, HTTP status: 403

Field

Error description

How to Fix

-

Access denied

The item does not exist or you have no permission to edit it. Check the item ID and permissions

Method Not Found

Error Code: BITRIX_REST_V3_EXCEPTION_METHODNOTFOUNDEXCEPTION, HTTP status: 404

Field

Error description

How to Fix

-

Method #METHOD# was not found

Check the method name, for example, crm.activity.binding.move

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