Delete Task tasks.task.delete
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:
tasksWho can execute the method: user with permission to delete a task
The method tasks.task.delete removes a task.
You can check the permission to delete a task using the task access check method.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
id* |
Task identifier. The task identifier can be obtained when creating a new task or through the old method of getting the list of tasks |
Code Examples
How to Use Examples in Documentation
The call to the new API differs by the addition of the /api/ parameter in the request:
https://{installation_address}/rest/api/{user_id}/{webhook_token}/tasks.task.delete
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"id":8131}' \
https://**put_your_bitrix24_address**/rest/api/**put_your_user_id_here**/**put_your_webhook_here**/tasks.task.delete
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"id":8131,"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/api/tasks.task.delete
The SDK does not yet support calls to the /rest/api/ address. Use direct HTTP requests, for example, via curl or fetch.
try
{
const response = await $b24.callMethod(
'tasks.task.delete',
{
id: 8131,
}
);
const result = response.getData().result;
console.log('Deleted task:', result);
processResult(result);
}
catch( error )
{
console.error('Error:', error);
}
The SDK does not yet support calls to the /rest/api/ address. Use direct HTTP requests, for example, via curl or fetch.
try {
$response = $b24Service
->core
->call(
'tasks.task.delete',
[
'id' => 8131
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error deleting task: ' . $e->getMessage();
}
The SDK does not yet support calls to the /rest/api/ address. Use direct HTTP requests, for example, via curl or fetch.
BX24.callMethod(
'tasks.task.delete',
{
id: 8131
},
function(result){
console.info(result.data());
console.log(result);
}
);
The SDK does not yet support calls to the /rest/api/ address. Use direct HTTP requests, for example, via curl or fetch.
require_once('crest.php');
$result = CRest::call(
'tasks.task.delete',
[
'id' => 8131
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP Status: 200
{
"result": {
"result": true
},
"time": {
"start": 1765366175,
"finish": 1765366176.329242,
"duration": 1.3292419910430908,
"processing": 1,
"date_start": "2025-12-10T14:29:35+01:00",
"date_finish": "2025-12-10T14:29:36+01:00",
"operating_reset_at": 1765366775,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Root element of the response. Contains an object with the key |
|
time |
Information about the request execution time |
Error Handling
HTTP Status: 400
{
"error": {
"code": "BITRIX_REST_V3_EXCEPTION_ACCESSDENIEDEXCEPTION",
"message": "Access denied"
}
}
|
Name |
Description |
|
error.code |
String error code. Use it to identify the type of exception |
|
error.message |
Text description of the error |
|
error.validation |
Array with error details. Present only in data validation errors |
|
error.validation[].field |
Name of the field where the validation error occurred |
|
error.validation[].message |
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 |
|
|
Required field |
Add |
|
|
Field |
Ensure the value is a number, not a string |
Access Error
Error Code: BITRIX_REST_V3_EXCEPTION_ACCESSDENIEDEXCEPTION
|
Field |
Error Description |
How to Fix |
|
|
Access denied |
No access to the task |
Statuses and System Error Codes
HTTP Status: 20x, 40x, 50x
The errors described below may occur when calling any method.
|
Status |
Code |
Description |
|
|
|
An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support |
|
|
|
An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
The current method is not permitted for calls using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The HTTPS protocol is required for method calls |
|
|
|
The REST API is blocked due to overload. This is a manual individual block; please contact Bitrix24 technical support to lift it |
|
|
|
The REST API is only available on commercial plans |
|
|
|
The user associated with the access token or webhook used to call the method lacks the necessary permissions |
|
|
|
The manifest is not available |
|
|
|
The request requires higher privileges than those provided by the webhook token |
|
|
|
The provided access token has expired |
|
|
|
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 |
|
|
|
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
- Check Access Permissions tasks.task.access.get
- Send a Message in Task Chat tasks.task.chat.message.send
- Update Task tasks.task.update