Update Shipment Property sale.shipmentproperty.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:
saleWho can execute the method: administrator
The method sale.shipmentproperty.update updates the shipment property.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
Identifier of the shipment property |
|
|
fields* |
Field values for updating the shipment property. The The method overwrites the property. The |
Parameter fields
General parameters applicable to shipment properties of any type:
Required parameters are marked with *
|
Name |
Description |
|
name* |
Name of the shipment property |
|
code |
Symbolic code of the shipment property |
|
active |
Indicator of whether the shipment property is active.
If not provided, the value is reset to |
|
util |
Indicator of whether the shipment property is a system property. System properties are not displayed in the public part.
If not provided, the value is reset to |
|
userProps |
Indicator of whether the shipment property is included in the customer profile.
If not provided, the value is reset to |
|
isFiltered |
Indicator of whether the shipment property is available in the filter on the shipment list page.
If not provided, the value is reset to |
|
sort |
Sort order of the property. If not provided, the value is reset to |
|
description |
Description of the shipment property |
|
required |
Indicator of whether filling in the shipment property value is mandatory.
If not provided, the value is reset to |
|
multiple |
Indicator of whether the shipment property is multiple. For multiple properties, it is possible to specify several values.
If not provided, the value is reset to |
|
xmlId |
External identifier of the shipment property |
|
defaultValue |
Default value of the shipment property. For multiple properties where |
|
settings |
An object in the format {"field_1": "value_1", ... "field_N": "value_N"} for passing additional settings for the shipment property. The list of supported keys for this object depends on the property type. The |
Parameters applicable to shipment properties of type STRING
|
Name |
Description |
|
isProfileName |
Indicator of whether the value of this shipment property should be used as the user's profile name.
If not provided, the value is reset to |
|
isPayer |
Indicator of whether the value of this shipment property should be used as the payer's name.
If not provided, the value is reset to |
|
isEmail |
Indicator of whether the value of this shipment property should be used as an e-mail (e.g., when registering a new user during order placement).
If not provided, the value is reset to |
|
isPhone |
Indicator of whether the value of this shipment property should be used as a phone number.
If not provided, the value is reset to |
|
isZip |
Indicator of whether the value of this shipment property should be used as a postal code.
If not provided, the value is reset to |
|
isAddress |
Indicator of whether the value of this shipment property should be used as an address.
If not provided, the value is reset to |
Parameters applicable to shipment properties of type LOCATION
|
Name |
Description |
|
isLocation |
Indicator of whether the value of this shipment property should be used as the customer's location for calculating delivery costs.
If not provided, the value is reset to |
|
isLocation4tax |
Indicator of whether the value of this shipment property should be used as the customer's location for determining tax rates.
If not provided, the value is reset to |
|
inputFieldLocation |
Deprecated field. Not used |
Parameters applicable to shipment properties of type ADDRESS
|
Name |
Description |
|
isAddressFrom |
Indicator of whether the value of this shipment property should be used as the customer's address from which the order needs to be picked up for calculating delivery costs.
If not provided, the value is reset to |
|
isAddressTo |
Indicator of whether the value of this shipment property should be used as the customer's address to which the order needs to be delivered for calculating delivery costs.
If not provided, the value is reset to |
Parameter settings
Parameters applicable to shipment properties of type STRING
|
Name |
Description |
|
minlength |
Minimum allowable length (number of characters) of the shipment property value |
|
maxlength |
Maximum allowable length (number of characters) of the shipment property value |
|
pattern |
Regular expression for validating the shipment property value. |
|
multiline |
Indicator of whether to display a multiline input field for the shipment property value.
If not provided, the value is reset to |
|
cols |
Deprecated parameter. Not used |
|
rows |
Deprecated parameter. Not used |
|
size |
Deprecated parameter. Not used |
Parameters applicable to shipment properties of type NUMBER
|
Name |
Description |
|
min |
Minimum allowable value for this shipment property |
|
max |
Maximum allowable value for this shipment property |
|
step |
Step for changing the value. Used in some user interfaces for convenience in changing the shipment property value |
Parameters applicable to shipment properties of type ENUM
|
Name |
Description |
|
multielement |
Indicator of whether to display the shipment property as a list of checkboxes.
If not provided, the value is reset to |
|
size |
Number of displayed values of the shipment property. Value is used in some user interfaces |
Parameters applicable to shipment properties of type FILE
|
Name |
Description |
|
maxsize |
Maximum allowable size of the uploaded file in bytes |
|
accept |
List of file extensions that are allowed to be uploaded as the value of this shipment property. Example: png, doc, zip |
Parameters applicable to shipment properties of type DATE
|
Name |
Description |
|
time |
Indicator of whether to add the option to select time when working with the value of this shipment property. Value is used in some user interfaces.
If not provided, the value is reset to |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"id":93,"fields":{"name":"Phone (for contacting the courier)","code":"PHONE","active":"Y","util":"N","userProps":"Y","isFiltered":"N","sort":500,"description":"property description","required":"Y","multiple":"N","settings":{"multiline":"Y","maxlength":100},"xmlId":"","defaultValue":"","isProfileName":"Y","isPayer":"Y","isEmail":"N","isPhone":"N","isZip":"N","isAddress":"N"}}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/sale.shipmentproperty.update
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"id":93,"fields":{"name":"Phone (for contacting the courier)","code":"PHONE","active":"Y","util":"N","userProps":"Y","isFiltered":"N","sort":500,"description":"property description","required":"Y","multiple":"N","settings":{"multiline":"Y","maxlength":100},"xmlId":"","defaultValue":"","isProfileName":"Y","isPayer":"Y","isEmail":"N","isPhone":"N","isZip":"N","isAddress":"N"},"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/sale.shipmentproperty.update
// 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
// Shape of the payload returned in result (match the "response handling" section of the page)
type ShipmentPropertyUpdateResult = {
property: {
active: string
code: string
defaultValue: string
description: string
id: number
inputFieldLocation: string
isAddress: string
isAddressFrom: string
isAddressTo: string
isEmail: string
isFiltered: string
isLocation: string
isLocation4tax: string
isPayer: string
isPhone: string
isProfileName: string
isZip: string
multiple: string
name: string
personTypeId: number
propsGroupId: number
required: string
settings: Record<string, string>
sort: number
type: string
userProps: string
util: string
xmlId: string
}
}
try {
const response = await $b24.actions.v2.call.make<ShipmentPropertyUpdateResult>({
method: 'sale.shipmentproperty.update',
params: {
id: 93,
fields: {
name: 'Phone (for courier contact)',
code: 'PHONE',
active: 'Y',
util: 'N',
userProps: 'Y',
isFiltered: 'N',
sort: 500,
description: 'property description',
required: 'Y',
multiple: 'N',
settings: {
multiline: 'Y',
maxlength: 100,
},
xmlId: '',
defaultValue: '',
isProfileName: 'Y',
isPayer: 'Y',
isEmail: 'N',
isPhone: 'N',
isZip: 'N',
isAddress: 'N',
},
},
requestId: Text.getUuidRfc4122()
})
// The payload is available only on a successful response
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
} else {
const result = response.getData()!.result
console.info('Updated property id:', result.property.id, 'name:', result.property.name)
}
} 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 updateShipmentProperty() {
try {
// Initialize the SDK inside a Bitrix24 frame
const $b24 = await B24Js.initializeB24Frame()
const response = await $b24.actions.v2.call.make({
method: 'sale.shipmentproperty.update',
params: {
id: 93,
fields: {
name: 'Phone (for courier contact)',
code: 'PHONE',
active: 'Y',
util: 'N',
userProps: 'Y',
isFiltered: 'N',
sort: 500,
description: 'property description',
required: 'Y',
multiple: 'N',
settings: {
multiline: 'Y',
maxlength: 100,
},
xmlId: '',
defaultValue: '',
isProfileName: 'Y',
isPayer: 'Y',
isEmail: 'N',
isPhone: 'N',
isZip: 'N',
isAddress: 'N',
},
},
requestId: B24Js.Text.getUuidRfc4122()
})
// The payload is available only on a successful response
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
return
}
const result = response.getData().result
console.info('Updated property id:', result.property.id, 'name:', result.property.name)
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
}
document.addEventListener('DOMContentLoaded', updateShipmentProperty)
</script>
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
fields = {
"name": "Phone (to contact the courier)",
"code": "PHONE",
"active": "Y",
"util": "N",
"userProps": "Y",
"isFiltered": "N",
"sort": 500,
"description": "property description",
"required": "Y",
"multiple": "N",
"settings": {
"multiline": "Y",
"maxlength": 100,
},
"xmlId": "",
"defaultValue": "",
"isProfileName": "Y",
"isPayer": "Y",
"isEmail": "N",
"isPhone": "N",
"isZip": "N",
"isAddress": "N",
}
try:
bitrix_response = client.sale.shipmentproperty.update(
bitrix_id=93,
fields=fields,
).response
result = bitrix_response.result
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(
'sale.shipmentproperty.update',
[
'id' => 93,
'fields' => [
'name' => 'Phone (for contacting the courier)',
'code' => 'PHONE',
'active' => 'Y',
'util' => 'N',
'userProps' => 'Y',
'isFiltered' => 'N',
'sort' => 500,
'description' => 'property description',
'required' => 'Y',
'multiple' => 'N',
'settings' => [
'multiline' => 'Y',
'maxlength' => 100
],
'xmlId' => '',
'defaultValue' => '',
'isProfileName' => 'Y',
'isPayer' => 'Y',
'isEmail' => 'N',
'isPhone' => 'N',
'isZip' => 'N',
'isAddress' => 'N',
],
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error updating shipment property: ' . $e->getMessage();
}
BX24.callMethod(
'sale.shipmentproperty.update', {
id: 93,
fields: {
name: 'Phone (for contacting the courier)',
code: 'PHONE',
active: 'Y',
util: 'N',
userProps: 'Y',
isFiltered: 'N',
sort: 500,
description: 'property description',
required: 'Y',
multiple: 'N',
settings: {
multiline: 'Y',
maxlength: 100
},
xmlId: '',
defaultValue: '',
isProfileName: 'Y',
isPayer: 'Y',
isEmail: 'N',
isPhone: 'N',
isZip: 'N',
isAddress: 'N',
}
},
function(result) {
if (result.error()) {
console.error(result.error());
} else {
console.info(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'sale.shipmentproperty.update',
[
'id' => 93,
'fields' => [
'name' => 'Phone (for contacting the courier)',
'code' => 'PHONE',
'active' => 'Y',
'util' => 'N',
'userProps' => 'Y',
'isFiltered' => 'N',
'sort' => 500,
'description' => 'property description',
'required' => 'Y',
'multiple' => 'N',
'settings' => [
'multiline' => 'Y',
'maxlength' => 100
],
'xmlId' => '',
'defaultValue' => '',
'isProfileName' => 'Y',
'isPayer' => 'Y',
'isEmail' => 'N',
'isPhone' => 'N',
'isZip' => 'N',
'isAddress' => 'N',
]
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
// client and ctx are already created — see the Go SDK section
res, err := client.Core().Call(ctx, "sale.shipmentproperty.update", b24.Params{
"id": 93,
"fields": b24.Params{
"name": "Phone (for contacting the courier)",
"code": "PHONE",
"active": "Y",
"util": "N",
"userProps": "Y",
"isFiltered": "N",
"sort": 500,
"description": "property description",
"required": "Y",
"multiple": "N",
"settings": b24.Params{
"multiline": "Y",
"maxlength": 100,
},
"xmlId": "",
"defaultValue": "",
"isProfileName": "Y",
"isPayer": "Y",
"isEmail": "N",
"isPhone": "N",
"isZip": "N",
"isAddress": "N",
},
})
if err != nil {
return fmt.Errorf("sale.shipmentproperty.update: %w", err)
}
// The method wraps the response in an object with the "property" key.
raw, ok := b24.Unwrap(res.Result, "property")
if !ok {
return fmt.Errorf("no property key in the response")
}
var item struct {
Active string `json:"active"`
Code string `json:"code"`
DefaultValue string `json:"defaultValue"`
Description string `json:"description"`
ID b24.ID `json:"id"`
InputFieldLocation string `json:"inputFieldLocation"`
}
if err := json.Unmarshal(raw, &item); err != nil {
return fmt.Errorf("parse response: %w", err)
}
fmt.Println(item.Active, item.Code)
Successful Response
HTTP status: 200
{
"result":{
"property":{
"active":"Y",
"code":"PHONE",
"defaultValue":"",
"description":"property description",
"id":96,
"inputFieldLocation":"0",
"isAddress":"N",
"isAddressFrom":"N",
"isAddressTo":"N",
"isEmail":"N",
"isFiltered":"N",
"isLocation":"N",
"isLocation4tax":"N",
"isPayer":"Y",
"isPhone":"N",
"isProfileName":"Y",
"isZip":"N",
"multiple":"N",
"name":"Phone (for contacting the courier)",
"personTypeId":3,
"propsGroupId":6,
"required":"Y",
"settings":{
"maxlength":"100",
"multiline":"Y"
},
"sort":500,
"type":"STRING",
"userProps":"Y",
"util":"N",
"xmlId":""
}
},
"time":{
"start":1712818736.235335,
"finish":1712818736.611224,
"duration":0.3758888244628906,
"processing":0.18679594993591309,
"date_start":"2024-04-11T09:58:56+02:00",
"date_finish":"2024-04-11T09:58:56+02:00"
}
}
Returned Data
|
Name |
Description |
|
result |
Root element of the response |
|
property |
Object with information about the updated shipment property. The fields are described in the sale_order_property type |
|
time |
Information about the request execution time |
Error Handling
HTTP status: 400
{
"error":200840400001,
"error_description":"property is not exists"
}
|
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 |
Possible Error Codes
|
Code |
Description |
|
|
The updated shipment property was not found |
|
|
Internal error updating the property |
|
|
Error occurs when trying to update a shipment property with the |
|
|
Error occurs when trying to update a shipment property with the |
|
|
Error occurs when trying to update a shipment property of type |
|
|
Error occurs when trying to update a shipment property of type |
|
|
Error occurs when trying to update a shipment property of type |
|
|
Error occurs when trying to update a shipment property of type |
|
|
Error occurs when trying to update a shipment property of type |
|
|
Error occurs when trying to update a shipment property of type |
|
|
Insufficient permissions to update the shipment property |
|
|
The |
|
|
The |
|
|
Required fields are not provided |
|
|
Other errors (e.g., fatal errors) |
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 |
Continue Learning
- Shipping Properties in the Online Store: Overview of Methods
- Add Shipment Property sale.shipmentproperty.add
- Get Shipment Property sale.shipmentproperty.get
- Get a list of shipment properties sale.shipmentproperty.list
- Delete Shipment Property sale.shipmentproperty.delete
- Get Fields and Settings of Shipment Property for a Specific Property Type sale.shipmentproperty.getfieldsbytype