Create Notifications for Delivery Request sale.delivery.request.sendmessage
Scope:
sale, deliveryWho can execute the method: administrator
This method creates notifications for a delivery request.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
DELIVERY_ID* |
Identifier of the delivery service related to the delivery request. You can obtain the identifiers of |
|
REQUEST_ID* |
Identifier of the delivery request. The identifier is assigned by the external system in response to the webhook for creating a delivery order (more details in the webhook description Creating a Delivery Order). |
|
ADDRESSEE* |
Recipient of the message. Possible values:
|
|
MESSAGE* |
Message (detailed description provided below) |
MESSAGE Parameter
Required parameters are marked with *
|
Name |
Description |
|
SUBJECT* |
Subject of the message. At least one of the following fields must be filled: |
|
BODY* |
Body of the message. The body of the message may use macros to replace time and monetary values. At least one of the following fields must be filled: |
|
STATUS |
Status of the message (detailed description provided below) |
|
MONEY_VALUES |
Object in the format Used to replace monetary values in the body of the message (see example below) |
STATUS Parameter
Required parameters are marked with *
|
Name |
Description |
|
MESSAGE* |
Text name of the message status |
|
SEMANTIC* |
Value of the status semantics. Possible values:
|
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"DELIVERY_ID":225,"REQUEST_ID":"4757aca4931a4f029f49c0db4374d13d","ADDRESSEE":"MANAGER","MESSAGE":{"SUBJECT":"Your order is on its way","BODY":"Estimated delivery price: #MONEY#","MONEY_VALUES":{"#MONEY#":351.2},"STATUS":{"MESSAGE":"Success","SEMANTIC":"success"}}}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/sale.delivery.request.sendmessage
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"DELIVERY_ID":225,"REQUEST_ID":"4757aca4931a4f029f49c0db4374d13d","ADDRESSEE":"MANAGER","MESSAGE":{"SUBJECT":"Your order is on its way","BODY":"Estimated delivery price: #MONEY#","MONEY_VALUES":{"#MONEY#":351.2},"STATUS":{"MESSAGE":"Success","SEMANTIC":"success"}},"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/sale.delivery.request.sendmessage
try
{
const response = await $b24.callMethod(
'sale.delivery.request.sendmessage', {
DELIVERY_ID: 225,
REQUEST_ID: "4757aca4931a4f029f49c0db4374d13d",
ADDRESSEE: "MANAGER",
MESSAGE: {
SUBJECT: "Your order is on its way",
BODY: "Estimated delivery price: #MONEY#",
MONEY_VALUES: {
"#MONEY#": 351.2,
},
STATUS: {
MESSAGE: "Success",
SEMANTIC: "success",
},
},
}
);
const result = response.getData().result;
if (result.error()) {
console.error(result.error());
} else {
console.info(result);
}
}
catch( error )
{
console.error(error);
}
try {
$response = $b24Service
->core
->call(
'sale.delivery.request.sendmessage',
[
'DELIVERY_ID' => 225,
'REQUEST_ID' => "4757aca4931a4f029f49c0db4374d13d",
'ADDRESSEE' => "MANAGER",
'MESSAGE' => [
'SUBJECT' => "Your order is on its way",
'BODY' => "Estimated delivery price: #MONEY#",
'MONEY_VALUES' => [
"#MONEY#" => 351.2,
],
'STATUS' => [
'MESSAGE' => "Success",
'SEMANTIC' => "success",
],
],
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error sending delivery message: ' . $e->getMessage();
}
BX24.callMethod(
'sale.delivery.request.sendmessage', {
DELIVERY_ID: 225,
REQUEST_ID: "4757aca4931a4f029f49c0db4374d13d",
ADDRESSEE: "MANAGER",
MESSAGE: {
SUBJECT: "Your order is on its way",
BODY: "Estimated delivery price: #MONEY#",
MONEY_VALUES: {
"#MONEY#": 351.2,
},
STATUS: {
MESSAGE: "Success",
SEMANTIC: "success",
},
},
},
function(result) {
if (result.error()) {
console.error(result.error());
} else {
console.info(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'sale.delivery.request.sendmessage',
[
'DELIVERY_ID' => 225,
'REQUEST_ID' => "4757aca4931a4f029f49c0db4374d13d",
'ADDRESSEE' => "MANAGER",
'MESSAGE' => [
'SUBJECT' => "Your order is on its way",
'BODY' => "Estimated delivery price: #MONEY#",
'MONEY_VALUES' => [
"#MONEY#" => 351.2,
],
'STATUS' => [
'MESSAGE' => "Success",
'SEMANTIC' => "success",
],
],
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP status: 200
{
"result":true,
"time":{
"start":1714561617.200821,
"finish":1714561617.526123,
"duration":0.3253021240234375,
"processing":0.1471860408782959,
"date_start":"2024-05-01T14:06:57+02:00",
"date_finish":"2024-05-01T14:06:57+02:00"
}
}
Returned Data
|
Name |
Description |
|
result |
Result of sending the message for the delivery request |
|
time |
Information about the execution time of the request |
Error Handling
HTTP status: 400, 403
{
"error":"DELIVERY_NOT_FOUND",
"error_description":"Delivery service has not been 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 |
Status |
|
|
Delivery service identifier not specified |
|
|
|
Delivery service not found |
|
|
|
Delivery request identifier not specified |
|
|
|
Delivery request not found |
|
|
|
Message recipient not specified |
|
|
|
Unknown message recipient. Allowed values:
|
|
|
|
Message not specified. Either the subject or the body of the message must be specified |
|
|
|
Message status not specified |
|
|
|
Message status semantics not specified |
|
|
|
Unknown message status semantics |
|
|
|
Shipments linked to the specified delivery request not found |
|
|
|
Insufficient rights to add the delivery service |
|
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
- Update Delivery Request sale.delivery.request.update
- Delete delivery request sale.delivery.request.delete