Add Order Binding to CRM Object crm.orderentity.add

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

Who can execute the method: online store administrator

This method adds a binding of an order to a CRM object.

Method Parameters

Required parameters are marked with *

Name `type`	Description
fields* `object`	Field values for creating the binding

Parameter fields

Required parameters are marked with *

Name `type`	Description
orderId* `sale_order.id`	Order identifier
ownerTypeId* `integer`	Identifier of the CRM object type. Binding is only possible to a deal or invoice
ownerId* `integer`	Identifier of the CRM object. For deals, it can be obtained using the crm.deal.list method. For invoices, it can be obtained using the crm.invoice.list

Code Examples

How to Use Examples in Documentation

Add order binding to a deal:

cURL (Webhook)

cURL (OAuth)

BX24.js

PHP CRest

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"fields":{"orderId":5125,"ownerId":6933,"ownerTypeId":2}}' \
        https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/crm.orderentity.add

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"fields":{"orderId":5125,"ownerId":6933,"ownerTypeId":2},"auth":"**put_access_token_here**"}' \
        https://**put_your_bitrix24_address**/rest/crm.orderentity.add

try
        {
        	const response = await $b24.callMethod(
        		"crm.orderentity.add",
        		{
        			fields: {
        				orderId: 5125,
        				ownerId: 6933,
        				ownerTypeId: 2
        			}
        		}
        	);
        	
        	const result = response.getData().result;
        	console.log(result);
        }
        catch( error )
        {
        	console.error(error);
        }

BX24.callMethod(
            "crm.orderentity.add",
            {
                fields: {
                    orderId: 5125,
                    ownerId: 6933,
                    ownerTypeId: 2
                }
            },
        )
            .then(
                function(result)
                {
                    if (result.error())
                    {
                        console.error(result.error());
                    }
                    else
                    {
                        console.log(result);
                    }
                },
                function(error)
                {
                    console.info(error);
                }
            );

require_once('crest.php');
        
        $result = CRest::call(
            'crm.orderentity.add',
            [
                'fields' => [
                    'orderId' => 5125,
                    'ownerId' => 6933,
                    'ownerTypeId' => 2
                ]
            ]
        );
        
        echo '<PRE>';
        print_r($result);
        echo '</PRE>';

Response Handling

HTTP status: 200

{
            "result": {
                "dealOrder": {
                    "orderId": 5125,
                    "ownerId": 6933,
                    "ownerTypeId": 2
                }
            },
            "time": {
                "start": 1719325851.568441,
                "finish": 1719325852.546479,
                "duration": 0.9780380725860596,
                "processing": 0.32780981063842773,
                "date_start": "2024-06-25T16:30:51+02:00",
                "date_finish": "2024-06-25T16:30:52+02:00",
                "operating": 0
            }
        }

Returned Data

Name `type`	Description
result `object`	Root element of the response
dealOrder `crm_orderentity`	Object with information about the created binding
time `time`	Information about the request execution time

Error Handling

HTTP status: 400

{
            "error": "201650000001",
            "error_description": "Duplicate entry for key [ownerId, ownerTypeId, orderId]"
        }

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 Errors

Code	Description
`200040300020`	`Access Denied` Insufficient access permissions
`201650000001`	`Duplicate entry for key [ownerId, ownerTypeId, orderId]` Binding already exists
`200540400001`	`order does not exist` Order not found
`0`	`Required fields: #FIELDS#` Required fields not specified (`#FIELDS#` — list of fields separated by commas)
`0`	Various order saving errors

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

Overview of Methods

Retrieve List of Order Links to CRM Entities

Add Order Binding to CRM Object crm.orderentity.add

Method ParametersMethod Parameters

Parameter fieldsParameter fields

Code ExamplesCode Examples

Response HandlingResponse Handling

Returned DataReturned Data

Error HandlingError Handling

Possible ErrorsPossible Errors

Statuses and System Error CodesStatuses and System Error Codes

Continue LearningContinue Learning