Update a Bank Detail v 3.0 crm.[type].requisite.bankrequisite.update
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:
crmWho can execute the method: a user with permission to edit the contact or company that owns the requisite
This method belongs to REST 3.0. The call specifics and response format of the new API version are described in the REST 3.0 overview.
The crm.<type>.requisite.bankrequisite.update method updates the fields of a bank detail and returns it after saving. The method changes only the fields you pass.
Method Name for the Object Type
|
Object type |
Method |
|
Company |
|
|
Contact |
|
Bank details belong to requisites of contacts and companies. The company or contact segment of the method name must match the owner of the requisite: a crm.contact.* method does not find a bank detail of a company.
The method name is written in lowercase: crm.company.requisite.bankrequisite.update, not crm.company.requisite.bankRequisite.update. If the name is written in a different case, the method returns the "Method Not Found" error.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
id* |
Bank detail ID. You can retrieve the ID with the crm.<type>.requisite.bankrequisite.list method |
|
fields* |
Object with the new field values. Pass at least one field. You can change The |
Code Examples
How to Use Examples in Documentation
The new API call differs by adding the /api/ segment to the request URL:
https://{installation_address}/rest/api/{user_id}/{webhook_token}/crm.company.requisite.bankrequisite.update
The examples add a comment and a bank address to bank detail 23. For a contact, replace the method name with crm.contact.requisite.bankrequisite.update.
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"id":23,"fields":{"comments":"For supplier payments","bankAddress":"Kurfürstendamm 21, 10719 Berlin, Germany"}}' \
https://**put_your_bitrix24_address**/rest/api/**put_your_user_id_here**/**put_your_webhook_here**/crm.company.requisite.bankrequisite.update
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"id":23,"fields":{"comments":"For supplier payments","bankAddress":"Kurfürstendamm 21, 10719 Berlin, Germany"},"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/api/crm.company.requisite.bankrequisite.update
CRM methods are not yet included in the list of REST 3.0 methods known to $b24.actions.v3.call.make: such a call returns the SDK error JSSDK_CORE_METHOD_NOT_SUPPORT_IN_API_V3. Call the method through the REST 3.0 HTTP client — $b24.getHttpClient(ApiVersion.v3).call.
import { ApiVersion, Text } from '@bitrix24/b24jssdk'
import type { B24Frame } from '@bitrix24/b24jssdk'
declare const $b24: B24Frame
type BankRequisiteUpdateResult = {
item: {
id: number
requisiteId: number
name: string
bankName: string | null
iban: string | null
bic: string | null
}
}
try {
const response = await $b24.getHttpClient(ApiVersion.v3).call<BankRequisiteUpdateResult>(
'crm.company.requisite.bankrequisite.update',
{
id: 23,
fields: {
comments: 'For supplier payments',
bankAddress: 'Kurfürstendamm 21, 10719 Berlin, Germany',
},
},
Text.getUuidRfc4122()
)
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
} else {
const result = response.getData()!.result
console.info('Bank requisite updated:', result.item)
}
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
CRM methods are not yet included in the list of REST 3.0 methods known to $b24.actions.v3.call.make. Call the method through the REST 3.0 HTTP client — $b24.getHttpClient(B24Js.ApiVersion.v3).call.
<script src="https://unpkg.com/@bitrix24/b24jssdk@1/dist/umd/index.min.js"></script>
<script>
async function updateBankRequisite() {
try {
const $b24 = await B24Js.initializeB24Frame()
const response = await $b24.getHttpClient(B24Js.ApiVersion.v3).call(
'crm.company.requisite.bankrequisite.update',
{
id: 23,
fields: {
comments: 'For supplier payments',
bankAddress: 'Kurfürstendamm 21, 10719 Berlin, Germany',
},
},
B24Js.Text.getUuidRfc4122()
)
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
return
}
const result = response.getData().result
console.info('Bank requisite updated:', result.item)
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
}
document.addEventListener('DOMContentLoaded', updateBankRequisite)
</script>
b24pysdk has no ready-made wrappers for CRM methods, and the SDK sends to REST 3.0 only the methods from the Config().api_v3_methods list. Add the method to this list and call it via bitrix_token.call_method with prefer_version=3.
from b24pysdk import Config
from b24pysdk.errors import BitrixSDKException
from b24pysdk.errors.v3 import BitrixAPIError
method = "crm.company.requisite.bankrequisite.update"
Config().configure(api_v3_methods=Config().api_v3_methods | {method})
try:
response = bitrix_token.call_method(
api_method=method,
params={
"id": 23,
"fields": {
"comments": "For supplier payments",
"bankAddress": "Kurfürstendamm 21, 10719 Berlin, Germany",
},
},
prefer_version=3,
)
result = response["result"]
print(result)
except BitrixAPIError as error:
print(
"Bitrix API error",
f"code: {error.code}",
f"message: {error.error.message}",
sep="\n",
)
except BitrixSDKException as error:
print(f"Bitrix SDK error: {error.message}")
except Exception as error:
print(f"Unexpected error: {error}")
SDKs do not yet support the /rest/api/ address in calls. Use direct HTTP requests, for example, via curl or fetch.
try {
$response = $b24Service
->core
->call(
'crm.company.requisite.bankrequisite.update',
[
'id' => 23,
'fields' => [
'comments' => 'For supplier payments',
'bankAddress' => 'Kurfürstendamm 21, 10719 Berlin, Germany',
],
]
);
$result = $response
->getResponseData()
->getResult();
print_r($result);
} catch (Throwable $e) {
echo $e->getMessage();
}
SDKs do not yet support the /rest/api/ address in calls. Use direct HTTP requests, for example, via curl or fetch.
BX24.callMethod(
'crm.company.requisite.bankrequisite.update',
{
id: 23,
fields: {
comments: 'For supplier payments',
bankAddress: 'Kurfürstendamm 21, 10719 Berlin, Germany',
},
},
result => {
if (result.error())
console.error(result.error());
else
console.dir(result.data());
}
);
SDKs do not yet support the /rest/api/ address in calls. Use direct HTTP requests, for example, via curl or fetch.
require_once('crest.php');
$result = CRest::call(
'crm.company.requisite.bankrequisite.update',
[
'id' => 23,
'fields' => [
'comments' => 'For supplier payments',
'bankAddress' => 'Kurfürstendamm 21, 10719 Berlin, Germany',
],
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
// client and ctx are already created — see the Go SDK section
res, err := client.Core().Call(ctx, "crm.company.requisite.bankrequisite.update", b24.Params{
"id": 23,
"fields": b24.Params{
"comments": "For supplier payments",
"bankAddress": "Kurfürstendamm 21, 10719 Berlin, Germany",
},
})
if err != nil {
return fmt.Errorf("crm.company.requisite.bankrequisite.update: %w", err)
}
var result struct {
Item struct {
ID int `json:"id"`
RequisiteID int `json:"requisiteId"`
Name string `json:"name"`
BankName *string `json:"bankName"`
Iban *string `json:"iban"`
Bic *string `json:"bic"`
} `json:"item"`
}
if err := json.Unmarshal(res.Result, &result); err != nil {
return fmt.Errorf("parse response: %w", err)
}
fmt.Println(result.Item.ID, result.Item.Name)
Response Handling
HTTP status: 200
{
"result": {
"item": {
"id": 23,
"requisiteId": 549,
"name": "Main account",
"comments": "For supplier payments",
"bankName": "Berliner Handelsbank AG",
"bankAddress": "Kurfürstendamm 21, 10719 Berlin, Germany",
"bankRoutingNumber": "37040044",
"bankAccountHolderName": "Müller GmbH",
"bankAccountNumber": "0532013000",
"iban": "DE89370400440532013000",
"swift": null,
"bic": "COBADEFFXXX"
}
},
"time": {
"start": 1793711900,
"finish": 1793711900.089311,
"duration": 0.08931088447570801,
"processing": 0,
"date_start": "2026-11-03T16:18:20+03:00",
"date_finish": "2026-11-03T16:18:20+03:00",
"operating_reset_at": 1793712480,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Object with response data |
|
result.item |
The bank detail after saving, with all fields available for the country of the requisite template. Empty fields are returned as |
|
time |
Information about the request execution time |
Error Handling
HTTP status: 400
{
"error": {
"code": "BITRIX_REST_V3_EXCEPTION_VALIDATION_REQUESTVALIDATIONEXCEPTION",
"message": "Error validating request object.",
"validation": [
{
"message": "A bank requisite cannot be moved to another requisite.",
"field": "requisiteId"
}
]
}
}
|
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 |
Pass the bank detail |
|
|
This request requires data type |
Pass the ID as a number |
|
|
The fields property must not be empty |
Pass at least one field in |
|
|
A bank requisite cannot be moved to another requisite |
Remove |
|
|
The bank requisite field is not available in the current template |
The field is not in the set of bank fields for the country of the requisite template, for example, |
Object Validation Errors
Error Code: BITRIX_REST_V3_EXCEPTION_VALIDATION_DTOVALIDATIONEXCEPTION
|
Field |
Error description |
How to Fix |
|
|
Field value must not be empty |
Pass a non-empty |
|
|
String must not be longer than 11 characters |
Shorten the value to the specified length |
Bank Detail Not Found
Error Code: BITRIX_REST_V3_EXCEPTION_ENTITYNOTFOUNDEXCEPTION
|
Field |
Error description |
How to Fix |
|
|
Entity with ID |
The bank detail does not exist, belongs to an owner of a different type, or you do not have permission to edit the owner. Check |
Unknown Field Error
Error Code: BITRIX_REST_V3_EXCEPTION_UNKNOWNDTOPROPERTYEXCEPTION
|
Field |
Error description |
How to Fix |
|
|
Unknown field |
Check the field name against the bank detail field descriptions |
Method Not Found
Error Code: BITRIX_REST_V3_EXCEPTION_METHODNOTFOUNDEXCEPTION, HTTP status: 404
|
Field |
Error description |
How to Fix |
|
|
Method |
Check the method name: it is written in lowercase, for example, |
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 |