Conduct Warehouse Accounting Document catalog.document.conduct

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

Who can execute the method:

a user with the "Conduct Document" access permission for the document type in the request,

and "View and Select Warehouse" access permission for the incoming or outgoing warehouse.

The method catalog.document.conduct conducts a warehouse accounting document:

the document status changes to Y — conducted,
the warehouse stock of goods is updated according to the document's items.

Method Parameters

Required parameters are marked with *

Name `type`	Description
id* `catalog_document.id`	Document identifier, can be obtained using the catalog.document.list method

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 '{"id":142}' \
        https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/catalog.document.conduct

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"id":142,"auth":"**put_access_token_here**"}' \
        https://**put_your_bitrix24_address**/rest/catalog.document.conduct

try
        {
        	const response = await $b24.callMethod(
        		'catalog.document.conduct',
        		{ id: 142 }
        	);
        
        	const result = response.getData().result;
        	console.log(result);
        }
        catch (error)
        {
        	console.error(error);
        }

try {
            $response = $b24Service
                ->core
                ->call(
                    'catalog.document.conduct',
                    [
                        'id' => 142,
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            if ($result === true) {
                echo 'Document conducted';
            }
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error conducting document: ' . $e->getMessage();
        }

BX24.callMethod(
            'catalog.document.conduct',
            { id: 142 },
            function(result)
            {
                if (result.error())
                    console.error(result.error());
                else
                    console.log(result.data());
            }
        );

require_once('crest.php');
        
        $result = CRest::call(
            'catalog.document.conduct',
            [
                'id' => 142,
            ]
        );
        
        echo '<PRE>';
        print_r($result);
        echo '</PRE>';

Response Handling

HTTP Code: 200

{
            "result": true,
            "time": {
                "start": 1762409135,
                "finish": 1762409136.304248,
                "duration": 1.3042480945587158,
                "processing": 1,
                "date_start": "2025-11-06T09:05:35+01:00",
                "date_finish": "2025-11-06T09:05:36+01:00",
                "operating_reset_at": 1762409735,
                "operating": 0.3091859817504883
            }
        }

Returned Data

Name `type`	Description
result `boolean`	Root element of the response, contains `true` if the document is conducted
time `time`	Information about the request execution time

Error Handling

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

HTTP Code: 400

{
            "error": "0",
            "error_description": "Document not found"
        }

Possible Error Codes

Code	Description	Value
`0`	Failed to complete the action as you do not have sufficient rights to view and select warehouses	No rights to work with the warehouse of the goods from the document
`0`	Insufficient rights to save the document	No rights to the product catalog, warehouse accounting, or no rights to conduct the document
`0`	Document not found	A non-existent document identifier was specified
`0`	Document conducting error: "error text"	The document contains incorrect data, for example, "Supplier not specified"
`0`	Warehouse accounting is not available on your plan	Warehouse accounting is not available on your plan
`0`	Warehouse accounting must be enabled to conduct the document	Warehouse accounting must be enabled to conduct the document

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

Perform bulk cancellation of documents

Perform bulk processing of documents

Conduct Warehouse Accounting Document catalog.document.conduct

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