Delete a Signing Provider sign.b2e.provider.delete
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:
sign.b2eWho can execute the method: administrator
The method sign.b2e.provider.delete disconnects an external signing provider from Bitrix24.
The method works only in the context of the application authorization.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
id* |
Provider identifier. The identifier is returned by the sign.b2e.provider.add method, and the list of providers with identifiers is returned by the sign.b2e.provider.tail method |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"id":42,"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/sign.b2e.provider.delete
// 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
// On a sign service failure result holds error and error_description instead of true
type ProviderDeleteResult = boolean | { error: number, error_description: string }
try {
const response = await $b24.actions.v2.call.make<ProviderDeleteResult>({
method: 'sign.b2e.provider.delete',
params: {
id: 42,
},
requestId: Text.getUuidRfc4122()
})
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
} else {
const result = response.getData()!.result
if (result === true) {
console.info('Provider deleted')
} else if (typeof result === 'object') {
console.error(result.error_description)
}
}
} 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 deleteSignProvider() {
try {
const $b24 = await B24Js.initializeB24Frame()
const response = await $b24.actions.v2.call.make({
method: 'sign.b2e.provider.delete',
params: {
id: 42
},
requestId: B24Js.Text.getUuidRfc4122()
})
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
return
}
// On a sign service failure result holds error and error_description instead of true
const result = response.getData().result
if (result === true) {
console.info('Provider deleted')
} else if (typeof result === 'object') {
console.error(result.error_description)
}
} catch (error) {
console.error(error)
}
}
document.addEventListener('DOMContentLoaded', deleteSignProvider)
</script>
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
try:
bitrix_response = client.call(
"sign.b2e.provider.delete",
{
"id": 42,
},
).response
result = bitrix_response.result
# On a sign service failure result holds error and error_description
if isinstance(result, dict):
print(f"Sign service error: {result['error_description']}")
else:
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(
'sign.b2e.provider.delete',
[
'id' => 42
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error: ' . $e->getMessage();
}
BX24.callMethod(
'sign.b2e.provider.delete',
{
id: 42
},
result => {
if (result.error()) {
console.error(result.error());
} else {
console.dir(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'sign.b2e.provider.delete',
[
'id' => 42
]
);
if (isset($result['error'])) {
echo 'Error: ' . $result['error_description'];
} elseif (is_array($result['result'])) {
echo 'Sign service error: ' . $result['result']['error_description'];
} else {
echo 'Provider deleted';
}
// client and ctx are already created — see the Go SDK section
res, err := client.Core().Call(ctx, "sign.b2e.provider.delete", b24.Params{
"id": 42,
})
if err != nil {
return fmt.Errorf("sign.b2e.provider.delete: %w", err)
}
var ok bool
if err := json.Unmarshal(res.Result, &ok); err != nil {
// on a sign service failure result holds error and error_description
return fmt.Errorf("sign service response: %s", res.Result)
}
fmt.Println("provider deleted:", ok)
Response Handling
HTTP Status: 200
{
"result": true,
"time": {
"start": 1792738607,
"finish": 1792738608.01666,
"duration": 1.0166599750518799,
"processing": 1,
"date_start": "2026-10-23T09:56:47+03:00",
"date_finish": "2026-10-23T09:56:48+03:00",
"operating_reset_at": 1792739160,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Deletion result. |
|
time |
Information about the request execution time |
Error Handling
HTTP Status: 403
{
"error": "WRONG_AUTH_TYPE",
"error_description": "Current authorization type is denied for this method Application context required"
}
|
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 |
If the Bitrix24 sign service returns an error without its own code, the method responds with HTTP status 200, and result contains an object with the error and error_description fields instead of true. Consider the call successful only if result equals true.
{
"result": {
"error": 0,
"error_description": "External provider with id 42 doesnt exist"
},
"time": {
"start": 1792738607,
"finish": 1792738608.01666,
"duration": 1.0166599750518799,
"processing": 1,
"date_start": "2026-10-23T09:56:47+03:00",
"date_finish": "2026-10-23T09:56:48+03:00",
"operating_reset_at": 1792739160,
"operating": 0
}
}
If the error text contains the code SIGN_CLIENT_CONNECTION_ERROR, INCORRECT_JSON, INCORRECT_HTTP_STATUS, INCORRECT_DATA, or INCORRECT_REGISTER_RESPONSE, Bitrix24 did not receive a response from the service. The provider may have been deleted anyway. You can check this with the sign.b2e.provider.tail method.
Possible Error Codes
|
Status |
Code |
Description |
Value |
|
|
|
Current authorization type is denied for this method Application context required |
The method was called outside an application with OAuth authorization, for example, through a webhook |
|
|
|
Access denied! Access denied |
The user is not an administrator, or e-Signature for HR is not available on Bitrix24 |
|
|
|
Access denied! User authorization required |
The request was made without user authorization |
|
|
|
External provider with id #ID# doesnt exist |
The provider with the |
|
|
Sign service code |
Sign service error text |
The sign service did not delete the provider and returned its own error code |
|
|
|
Cannot perform action. Please try again later (error code: #CODE#). |
The sign service returned an error, or Bitrix24 did not receive its response. |
|
|
|
This action is not available yet, please try again later. |
The sign service version does not support this action yet |
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 |