Unregister the Connector imconnector.unregister

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

Who can execute the method: any user

The method imconnector.unregister removes a user connector.

This method works only in the context of the application.

Method Parameters

Required parameters are marked with *

Name
type

Description

ID*
string

The identifier of the connector that was provided during registration in imconnector.register

Code Examples

How to Use Examples in Documentation

curl -X POST \
          -H "Content-Type: application/json" \
          -H "Accept: application/json" \
          -d '{"ID":"myconnector","auth":"**put_access_token_here**"}' \
          https://**put_your_bitrix24_address**/rest/imconnector.unregister
        
const response = await $b24.callMethod('imconnector.unregister', {
          ID: 'myconnector',
        });
        console.log(response.getData());
        
$result = $b24Service->core->call(
            'imconnector.unregister',
            [
                'ID' => 'myconnector',
            ]
        );
        
BX24.callMethod(
            'imconnector.unregister',
            {
              ID: 'myconnector',
            },
            function(result) {
              console.log(result.data());
            }
        );
        
$result = CRest::call(
            'imconnector.unregister',
            [
                'ID' => 'myconnector',
            ]
        );

Response Handling

HTTP Status: 200

{
            "result": {
            "result": true
            },
            "time": {
            "start": 1738065600.11,
            "finish": 1738065600.25,
            "duration": 0.14,
            "processing": 0.06,
            "date_start": "2025-01-28T12:00:00+00:00",
            "date_finish": "2025-01-28T12:00:00+00:00"
            }
        }

Returned Data

Name
type

Description

result
boolean

true if the connector registration has been removed

time
time

Information about the request execution time

Error Handling

The method can return two error formats.

  1. HTTP Status: 200 with result = false
  {
              "result": {
                  "result": false,
                  "error": "APPLICATION_UNREGISTRATION_ERROR",
                  "error_description": "Error unregistering the application"
              }
          }
  1. HTTP Status: 403 for a system authorization error
  {
              "error": "WRONG_AUTH_TYPE",
              "error_description": "Current authorization type is denied for this method. Application context 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

200

APPLICATION_UNREGISTRATION_ERROR

Error unregistering the application

Failed to remove the connector by ID for the current application

200

NO_APPLICATION_ID

Failed to retrieve application ID

Application not found in the context of the request

403

WRONG_AUTH_TYPE

Current authorization type is denied for this method. Application context required.

Method called outside the context of the OAuth application

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

Previous
Get List of Connectors
Next
Send Messages to Bitrix24