Register Requisite Link with Object crm.requisite.link.register
Scope:
crmWho can execute the method: any user
This method registers a link between requisites and an object.
For successful registration, the requisite IDs must belong to the client and seller selected in the linked object. If a requisite is not available, its ID is passed as 0. You can even specify all requisite IDs as zero. In this case, it is considered that the requisites are not linked to the object.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
fields* |
A set of fields for the requisite link — an object of the form |
Parameter fields
Required parameters are marked with *
|
Name |
Description |
|
ENTITY_TYPE_ID* |
Identifier of the object type to which the link belongs. The following types can be used:
You can obtain CRM object type identifiers using the method crm.enum.ownertype |
|
ENTITY_ID* |
Identifier of the object to which the link belongs. Object identifiers can be obtained using the following methods: crm.deal.list, crm.quote.list, crm.item.list |
|
REQUISITE_ID* |
Identifier of the client's requisite selected for the object. Requisite identifiers can be obtained using the method crm.requisite.list |
|
BANK_DETAIL_ID* |
Identifier of the client's bank requisite selected for the object. Bank requisite identifiers can be obtained using the method crm.requisite.bankdetail.list |
|
MC_REQUISITE_ID* |
Identifier of my company's requisite selected for the object. Requisite identifiers can be obtained using the method crm.requisite.list |
|
MC_BANK_DETAIL_ID* |
Identifier of my company's bank requisite selected for the object. Bank requisite identifiers can be obtained using the method crm.requisite.bankdetail.list |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"fields":{"ENTITY_TYPE_ID":31,"ENTITY_ID":315,"REQUISITE_ID":60,"BANK_DETAIL_ID":24,"MC_REQUISITE_ID":2,"MC_BANK_DETAIL_ID":2}}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/crm.requisite.link.register
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"fields":{"ENTITY_TYPE_ID":31,"ENTITY_ID":315,"REQUISITE_ID":60,"BANK_DETAIL_ID":24,"MC_REQUISITE_ID":2,"MC_BANK_DETAIL_ID":2},"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/crm.requisite.link.register
try
{
const response = await $b24.callMethod(
"crm.requisite.link.register", {
fields: {
ENTITY_TYPE_ID: 31,
ENTITY_ID: 315,
REQUISITE_ID: 60,
BANK_DETAIL_ID: 24,
MC_REQUISITE_ID: 2,
MC_BANK_DETAIL_ID: 2
}
}
);
const result = response.getData().result;
console.dir(result);
}
catch( error )
{
console.error(error);
}
try {
$response = $b24Service
->core
->call(
'crm.requisite.link.register',
[
'fields' => [
'ENTITY_TYPE_ID' => 31,
'ENTITY_ID' => 315,
'REQUISITE_ID' => 60,
'BANK_DETAIL_ID' => 24,
'MC_REQUISITE_ID' => 2,
'MC_BANK_DETAIL_ID' => 2,
],
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error registering requisite link: ' . $e->getMessage();
}
BX24.callMethod(
"crm.requisite.link.register", {
fields: {
ENTITY_TYPE_ID: 31,
ENTITY_ID: 315,
REQUISITE_ID: 60, // Identifier of the requisite belonging to the buyer
BANK_DETAIL_ID: 24, // Identifier of the bank requisite belonging to the buyer
MC_REQUISITE_ID: 2, // Identifier of the requisite belonging to the selling company
MC_BANK_DETAIL_ID: 2 // Identifier of the bank requisite belonging to the selling company
}
},
function (result)
{
if (result.error())
console.error(result.error());
else
console.dir(result.data());
}
);
require_once('crest.php');
$result = CRest::call(
'crm.requisite.link.register',
[
'fields' =>
[
'ENTITY_TYPE_ID' => 31,
'ENTITY_ID' => 315,
'REQUISITE_ID' => 60,
'BANK_DETAIL_ID' => 24,
'MC_REQUISITE_ID' => 2,
'MC_BANK_DETAIL_ID' => 2
]
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP status: 200
{
"result": true,
"time": {
"start": 1718729280.575321,
"finish": 1718729281.296214,
"duration": 0.720893144607544,
"processing": 0.1967611312866211,
"date_start": "2024-06-18T18:48:00+02:00",
"date_finish": "2024-06-18T18:48:01+02:00",
"operating": 0.1967298984527588
}
}
Returned Data
|
Name |
Description |
|
result |
Result of the link registration:
|
|
time |
Information about the request execution time |
Error Handling
HTTP status: 40x, 50x
{
"error": "",
"error_description": "Entity is not found"
}
|
Name |
Description |
|
error |
String error code. It may consist of digits, Latin letters, and underscores |
|
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
|
Code |
Description |
|
|
Object type identifier is not set or has an invalid value |
|
|
Object identifier is not set or has an invalid value |
|
|
Client requisite identifier is not set or has an invalid value |
|
|
Client bank requisite identifier is not set or has an invalid value |
|
|
My company requisite identifier is not set or has an invalid value |
|
|
My company bank requisite identifier is not set or has an invalid value |
|
|
Client requisite with the specified identifier not found |
|
|
Client requisite with the specified identifier does not belong to the company specified in the object |
|
|
Client bank requisite with the specified identifier not found |
|
|
Client bank requisite with the specified identifier does not belong to the specified requisite |
|
|
My company requisite with the specified identifier not found |
|
|
My company requisite with the specified identifier does not belong to my company specified in the object |
|
|
My company bank requisite with the specified identifier not found |
|
|
My company bank requisite with the specified identifier does not belong to the specified requisite |
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 allowed to be called using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The methods must be called using the HTTPS protocol |
|
|
|
The REST API is blocked due to overload. This is a manual individual block, to remove it you need to contact Bitrix24 technical support |
|
|
|
The REST API is available only on commercial plans |
|
|
|
The user whose access token or webhook was used to call the method lacks 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 account administrator has allowed access to this application only for specific users |
|
|
|
The public part of the site is closed. To open the public part of the site on an on-premise installation, disable the option "Temporary closure of the public part of the site". Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site |
Continue Learning
- Get the link of the requisite with the object crm.requisite.link.get
- Get a list of links for requisites crm.requisite.link.list
- Unlink Requisite from Object crm.requisite.link.unregister
- Get Description of CRM Requisite Link Fields