Delete Sales Intelligence Trace crm.tracking.trace.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: crm

Who can execute the method:

any user can delete a trace

a user with permission to modify the object can delete the trace binding to the object

The method crm.tracking.trace.delete removes a Sales Intelligence trace.

Method Parameters

Required parameters are marked with *

Name
type

Description

id^*
integer

Identifier of the Sales Intelligence trace.

To fully delete the trace, permissions to modify all related objects are required.

The id can be obtained using the method crm.tracking.trace.add

Code Examples

How to Use Examples in Documentation

Example of deleting a Sales Intelligence trace, where:

id — identifier of the trace

cURL (Webhook)

cURL (OAuth)

PHP

BX24.js

PHP CRest

curl -X POST \
          -H "Content-Type: application/json" \
          -d '{
            "id": 125
          }' \
          "https://**put.your-domain-here**/rest/**user_id**/**webhook_code**/crm.tracking.trace.delete.json"

curl -X POST \
          -H "Content-Type: application/json" \
          -d '{
            "id": 125,
            "auth": "**put_access_token_here**"
          }' \
          "https://**put.your-domain-here**/rest/crm.tracking.trace.delete.json"

try
        {
        	const response = await $b24.callMethod(
        		'crm.tracking.trace.delete',
        		{
        			id: 125
        		}
        	);
        
        	const result = response.getData().result;
        	console.info(result);
        }
        catch (error)
        {
        	console.error(error);
        }

try {
            $response = $b24Service
                ->core
                ->call(
                    'crm.tracking.trace.delete',
                    [
                        'id' => 125,
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
            echo 'Success: ' . print_r($result, true);
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error deleting trace: ' . $e->getMessage();
        }

BX24.callMethod(
            'crm.tracking.trace.delete',
            {
                id: 125
            },
            function(result)
            {
                if (result.error())
                {
                    console.error(result.error());
                }
                else
                {
                    console.info(result.data());
                }
            }
        );

$result = CRest::call(
            'crm.tracking.trace.delete',
            [
                'id' => 125,
            ]
        );
        
        echo '<pre>';
        print_r($result);
        echo '</pre>';

Response Handling

HTTP Status: 200

{
            "result": null,
            "time": {
                "start": 1775119058,
                "finish": 1775119058.707133,
                "duration": 0.7071330547332764,
                "processing": 0,
                "date_start": "2026-04-02T11:37:38+02:00",
                "date_finish": "2026-04-02T11:37:38+02:00",
                "operating_reset_at": 1775119658,
                "operating": 0
            }
        }

Returned Data

Name
type

Description

result
null

The method does not return data in the response.

If no REST error occurred during the call, the result field returns null.

Upon successful deletion of the binding, the value is cleared in the "Sales Intelligence" field of the entity to which the trace was bound

time
time

Information about the request execution time

Error Handling

HTTP Status: 400

{
            "error": "ERROR_CORE",
            "error_description": "Parameter `id` required."
        }

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 Error Codes

Status	Code	Description	Value
`400`	`ERROR_CORE`	Parameter `id` required.	The `id` parameter is missing or an empty value was provided

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

Create a Sales Intelligence Trace

Determine the Current CRM Operating Mode

Delete Sales Intelligence Trace crm.tracking.trace.delete

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