Update Address for crm.address.update

Scope: crm

Who can execute the method: any user

This method updates the address for a contact or lead.

Method Parameters

Required parameters are marked with *

Name
type

Description

fields*
object

A set of fields — an object of the form {"field": "value"[, ...]} to update the address.

Values for the fields TYPE_ID, ENTITY_TYPE_ID, ENTITY_ID must be specified as they identify the address being modified. Other fields are specified if their values need to be changed

Parameter fields

Required parameters are marked with *

Name
type

Description

TYPE_ID*
integer

Identifier for the address type. Enumeration element "Address Type".

Enumeration elements for "Address Type" can be retrieved using the method crm.enum.addresstype

ENTITY_TYPE_ID*
integer

Identifier for the parent object type.

Object type identifiers can be retrieved using the method crm.enum.ownertype.

Addresses can only be linked to Contacts (which are linked to companies or contacts) or Leads.

For backward compatibility, the ability to link Addresses to Contacts or Companies has been retained. However, this linkage is only possible on some older accounts where the old address handling mode was specifically enabled by support.

ENTITY_ID*
string

Identifier for the parent object

ADDRESS_1
string

Street, house, building, structure

ADDRESS_2
string

Apartment / office

CITY
string

City

POSTAL_CODE
string

Postal code

REGION
string

District

PROVINCE
string

State

COUNTRY
string

Country

COUNTRY_CODE
string

Country code.

Not used, retained for backward compatibility. An empty string can be specified as a value.

LOC_ADDR_ID
integer

Identifier for the location address.

This field contains the identifier of the address object in the Location module, linked to the CRM address object. Each CRM address corresponds to an address object in the location module. This can be used to copy an existing address into CRM with location information that is not present in the CRM address fields.

If the identifier of the location module address is specified when creating an address, a copy of the location address is created and linked to the newly created CRM address. If no values are specified for the string address fields in this case, they will be filled from the location address.

If at least one string field is specified, only the specified fields will be saved in the CRM address, and their values will overwrite the corresponding values in the location address object. The same behavior will occur when updating the address.

Code Examples

How to Use Examples in Documentation

curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"fields":{"TYPE_ID":1,"ENTITY_TYPE_ID":3,"ENTITY_ID":1,"ADDRESS_1":"Street, 261","CITY":"Los Angeles"}}' \
        https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/crm.address.update
        
curl -X POST \
        -H "Content-Type: application/json" \
        -H "Accept: application/json" \
        -d '{"fields":{"TYPE_ID":1,"ENTITY_TYPE_ID":3,"ENTITY_ID":1,"ADDRESS_1":"Street, 261","CITY":"Los Angeles"},"auth":"**put_access_token_here**"}' \
        https://**put_your_bitrix24_address**/rest/crm.address.update
        
try
        {
        	const response = await $b24.callMethod(
        		"crm.address.update",
        		{
        			fields:
        			{
        				"TYPE_ID": 1,           //
        				"ENTITY_TYPE_ID": 3,    // - Identifying fields.
        				"ENTITY_ID": 1,         //
        				"ADDRESS_1": "Street, 261", // - Fields whose values are changing.
        				"CITY": "Los Angeles"                    //
        			}
        		}
        	);
        	
        	const result = response.getData().result;
        	if(result.error())
        	{
        		console.error(result.error());
        	}
        }
        catch(error)
        {
        	console.error('Error:', error);
        }
        
try {
            $response = $b24Service
                ->core
                ->call(
                    'crm.address.update',
                    [
                        'fields' => [
                            'TYPE_ID'        => 1,
                            'ENTITY_TYPE_ID' => 3,
                            'ENTITY_ID'      => 1,
                            'ADDRESS_1'      => 'Street, 261',
                            'CITY'           => 'Los Angeles',
                        ],
                    ]
                );
        
            $result = $response
                ->getResponseData()
                ->getResult();
        
        } catch (Throwable $e) {
            error_log($e->getMessage());
            echo 'Error updating address: ' . $e->getMessage();
        }
        
BX24.callMethod(
            "crm.address.update",
            {
                fields:
                {
                    "TYPE_ID": 1,           //
                    "ENTITY_TYPE_ID": 3,    // - Identifying fields.
                    "ENTITY_ID": 1,         //
                    "ADDRESS_1": "Street, 261", // - Fields whose values are changing.
                    "CITY": "Los Angeles"                    //
                }
            },
            function(result)
            {
                if(result.error())
                    console.error(result.error());
            }
        );
        
require_once('crest.php');
        
        $result = CRest::call(
            'crm.address.update',
            [
                'fields' => [
                    'TYPE_ID' => 1,
                    'ENTITY_TYPE_ID' => 3,
                    'ENTITY_ID' => 1,
                    'ADDRESS_1' => 'Street, 261',
                    'CITY' => 'Los Angeles'
                ]
            ]
        );
        
        echo '<PRE>';
        print_r($result);
        echo '</PRE>';
        

Response Handling

HTTP status: 200

{
            "result": true,
            "time": {
                "start": 1712922620.724857,
                "finish": 1712922623.393783,
                "duration": 2.6689260005950928,
                "processing": 2.210068941116333,
                "date_start": "2024-04-12T14:50:20+02:00",
                "date_finish": "2024-04-12T14:50:23+02:00"
            }
        }
        

Returned Data

Name
type

Description

result
boolean

Result of the address update:

  • true — updated
  • false — not updated

time
time

Information about the request execution time

Error Handling

HTTP status: 40x, 50x

{
            "error": "",
            "error_description": "ENTITY_ID is not defined or invalid."
        }
        

Name
type

Description

error
string

String error code. It may consist of digits, Latin letters, and underscores

error_description
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

TYPE_ID is not defined or invalid

Address type identifier is not specified or has an invalid value

ENTITY_TYPE_ID is not defined or invalid

Parent object type identifier is not specified or has an invalid value.

ENTITY_ID is not defined or invalid

Parent object identifier is not specified or has an invalid value.

TypeAddress not found

Address not found

Access denied

Insufficient access permissions to update the address

Statuses and System Error Codes

HTTP Status: 20x, 40x, 50x

The errors described below may occur when calling any method.

Status

Code
Error Message

Description

500

INTERNAL_SERVER_ERROR
Internal server error

An internal server error has occurred, please contact the server administrator or Bitrix24 technical support

500

ERROR_UNEXPECTED_ANSWER
Server returned an unexpected response

An internal server error has occurred, please contact the server administrator or Bitrix24 technical support

503

QUERY_LIMIT_EXCEEDED
Too many requests

The request intensity limit has been exceeded

405

ERROR_BATCH_METHOD_NOT_ALLOWED
Method is not allowed for batch usage

The current method is not allowed to be called using batch

400

ERROR_BATCH_LENGTH_EXCEEDED
Max batch length exceeded

The maximum length of parameters passed to the batch method has been exceeded

401

NO_AUTH_FOUND
Wrong authorization data

Invalid access token or webhook code

400

INVALID_REQUEST
Https required

The methods must be called using the HTTPS protocol

503

OVERLOAD_LIMIT
REST API is blocked due to overload

The REST API is blocked due to overload. This is a manual individual block, to remove it you need to contact Bitrix24 technical support

403

ACCESS_DENIED
REST API is available only on commercial plans

The REST API is available only on commercial plans

403

INVALID_CREDENTIALS
Invalid request credentials

The user whose access token or webhook was used to call the method lacks permissions

404

ERROR_MANIFEST_IS_NOT_AVAILABLE
Manifest is not available

The manifest is not available

403

insufficient_scope
The request requires higher privileges than provided by the webhook token

The request requires higher privileges than those provided by the webhook token

401

expired_token
The access token provided has expired

The provided access token has expired

403

user_access_error
The user does not have access to the application

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

500

PORTAL_DELETED
Portal was deleted

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