Cancel Processing of Multiple Documents catalog.document.cancelList
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:
catalogWho can execute the method: a user with the "View product catalog" and "View Inventory Management area" permissions and the "Cancel processing" permission for the required document type. The document must be available to the user under the "View" permission
The method catalog.document.cancelList cancels processing of multiple inventory documents.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
documentIds* |
Array of document IDs, for example Document IDs can be retrieved with the catalog.document.list method. The method accepts an empty array without an error and returns |
The method cancels processing of documents one by one, like catalog.document.cancel. If a document cannot be handled, the method moves on to the next one: processing of the other documents is canceled, and the response contains an error.
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"documentIds":[142,143,144]}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/catalog.document.cancelList
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"documentIds":[142,143,144],"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/catalog.document.cancelList
// This snippet is an ES module: top-level await requires type="module" or a bundler.
// $b24 is an already-initialized SDK instance (see the SDK "Get started" guide).
import { Text } from '@bitrix24/b24jssdk'
import type { B24Frame } from '@bitrix24/b24jssdk'
declare const $b24: B24Frame
try {
const response = await $b24.actions.v2.call.make<boolean>({
method: 'catalog.document.cancelList',
params: {
documentIds: [142, 143, 144],
},
requestId: Text.getUuidRfc4122()
})
// The payload is available only on a successful response
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
} else {
const result = response.getData()!.result
console.info('Documents cancelled successfully:', result)
}
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
<!-- Load the SDK (UMD build); it is exposed as the global B24Js -->
<script src="https://unpkg.com/@bitrix24/b24jssdk@1/dist/umd/index.min.js"></script>
<script>
async function cancelDocumentList() {
try {
// Initialize the SDK inside a Bitrix24 frame
const $b24 = await B24Js.initializeB24Frame()
const response = await $b24.actions.v2.call.make({
method: 'catalog.document.cancelList',
params: {
documentIds: [142, 143, 144],
},
requestId: B24Js.Text.getUuidRfc4122()
})
// The payload is available only on a successful response
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
return
}
const result = response.getData().result
console.info('Documents cancelled successfully:', result)
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
}
document.addEventListener('DOMContentLoaded', cancelDocumentList)
</script>
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
try:
bitrix_response = client.catalog.document.cancel_list(
document_ids=[
142,
143,
144,
],
).response
result = bitrix_response.result
print(result)
except BitrixAPIError as error:
print(
"Bitrix API error",
f"error: {error.error}",
f"error_description: {error.error_description}",
sep="\n",
)
except BitrixSDKException as error:
print(f"Bitrix SDK error: {error.message}")
except Exception as error:
print(f"Unexpected error: {error}")
try {
$response = $b24Service
->core
->call(
'catalog.document.cancelList',
[
'documentIds' => [142, 143, 144],
]
);
$result = $response
->getResponseData()
->getResult();
print_r($result);
} catch (Throwable $e) {
echo $e->getMessage();
}
BX24.callMethod(
'catalog.document.cancelList',
{ documentIds: [142, 143, 144] },
function(result)
{
if (result.error())
console.error(result.error());
else
console.log(result.data());
}
);
require_once('crest.php');
$result = CRest::call(
'catalog.document.cancelList',
[
'documentIds' => [142, 143, 144],
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
// client and ctx are already created — see the Go SDK section
res, err := client.Core().Call(ctx, "catalog.document.cancelList", b24.Params{
"documentIds": []int{142, 143, 144},
})
if err != nil {
return fmt.Errorf("catalog.document.cancelList: %w", err)
}
var ok bool
if err := json.Unmarshal(res.Result, &ok); err != nil {
return fmt.Errorf("parse response: %w", err)
}
fmt.Println("done:", ok)
Response Handling
HTTP status: 200
{
"result": true,
"time": {
"start": 1793883387,
"finish": 1793883387.934746,
"duration": 0.9347460269927979,
"processing": 0,
"date_start": "2026-11-05T15:56:27+03:00",
"date_finish": "2026-11-05T15:56:27+03:00",
"operating_reset_at": 1793883960,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Root element of the response. Contains |
|
time |
Information about the execution time of the request |
Error Handling
HTTP status: 400
{
"error": "0",
"error_description": "Error canceling inventory object \"Surplus stock adjustment\": The transaction is still pending.."
}
|
Name |
Description |
|
error |
String error code. It consists of digits, Latin letters, and underscores. It may arrive empty — in that case only |
|
error_description |
Error message for the developer. Do not show it to the end user without processing |
Possible Error Codes
|
Status |
Code |
Description |
Value |
|
|
|
Insufficient permissions to save the inventory object. |
The user does not have the "View product catalog" or "View Inventory Management area" permission |
|
|
|
Error canceling inventory object "Surplus stock adjustment": Insufficient permissions to save the inventory object.. |
The user does not have the "Cancel processing" permission for documents of this type |
|
|
|
Could not find value for parameter |
The |
|
|
|
Invalid value {abc} to match with parameter {documentIds}. Should be value of type array. |
|
|
|
|
Error canceling inventory object processing: Inventory object was not found.. |
The document is not found or is unavailable to the user |
|
|
|
Error canceling inventory object "Surplus stock adjustment": The transaction is still pending.. |
The document is not processed. The text contains the document name or, if it has none, the document type name |
|
|
|
Inventory Management is not available on your plan. |
Inventory Management is not available on the account plan |
|
|
|
You have to enable inventory management to process the inventory object. |
Inventory Management is disabled on the account. You can check the status with the catalog.document.mode.status method |
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 |
Description |
|
|
|
An internal server error has occurred. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support |
|
|
|
The server returned an unexpected response. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
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 |
|
|
|
The request contains no authorization data: neither an access token nor a webhook code was passed |
|
|
|
Methods are called over the HTTPS protocol only |
|
|
|
The REST API is blocked due to overload. This is a manual individual block. To have it lifted, contact Bitrix24 technical support |
|
|
|
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 — |
|
|
|
No active webhook with the specified user identifier and secret code was 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 |
|
|
|
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 |
|
|
|
The access token has expired |
|
|
|
The application is installed, but the Bitrix24 administrator has granted access to it only to specific users |
|
|
|
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 |