Update a location address

patch

/hcmRestApi/resources/11.13.18.05/locationsV2/{locationsV2UniqID}/child/addresses/{addressesUniqID}

Request

Path Parameters
  • The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
  • This is the hash key of the attributes which make up the composite key for the Locations V2 resource and used to uniquely identify an instance of Locations V2. The client should not generate the hash key value. Instead, the client should query on the Locations V2 collection resource in order to navigate to a specific instance of Locations V2 to get the hash key.
Header Parameters
  • This header accepts a string value. The string is a semi-colon separated list of =. It is used to perform effective date range operations. The accepted parameters are RangeMode, RangeSpan, RangeStartDate, RangeEndDate, RangeStartSequence and RangeEndSequence. The parameter values are always strings. The possible values for RangeMode are SET_LOGICAL_START, SET_LOGICAL_END, END_DATE, SET_EFFECTIVE_START, SET_EFFECTIVE_END, REPLACE_CORRECTION, REPLACE_UPDATE, RECONCILE_CORRECTION, CORRECTION, RECONCILE_UPDATE, UPDATE, ZAP and DELETE_CHANGES. The possible values for RangeSpan are PHYSICAL_ROW_END_DATE and LOGICAL_ROW_END_DATE. The values for RangeStartDate and RangeEndDate have to be a string representation of a date in yyyy-MM-dd format. The value for RangeStartSequence and RangeEndSequence must be strings such that when parsed they yield positive integers.
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • Title: Additional Address Attribute 1
    Maximum Length: 150
    Additional address attribute, used by localizations.
  • Title: Additional Address Attribute 2
    Maximum Length: 150
    Additional address attribute, used by localizations.
  • Title: Additional Address Attribute 3
    Maximum Length: 150
    Additional address attribute, used by localizations.
  • Title: Additional Address Attribute 4
    Maximum Length: 150
    Additional address attribute, used by localizations.
  • Title: Additional Address Attribute 5
    Maximum Length: 150
    Additional address attribute, used by localizations.
  • Title: Address Line 1
    Maximum Length: 240
    First line of the location address.
  • Title: Address Line 2
    Maximum Length: 240
    Second line of the location address.
  • Title: Address Line 3
    Maximum Length: 240
    Third line of the location address.
  • Title: Address Line 4
    Maximum Length: 240
    Fourth line of the location address.
  • Title: Building
    Maximum Length: 240
    Building name of the address.
  • Title: Effective End Date
    Effective end date for the location address.
  • Title: Effective Start Date
    Effective start date for the location address.
  • Title: Floor Number
    Maximum Length: 40
    Floor number of the address.
  • Title: Latitude
    Distance between the equator and a location address located to its north or south, expressed in degrees and minutes.
  • Title: Longitude
    Distance between the prime meridian and a location address located to its east or west, expressed in degrees and minutes.
  • Title: Long Postal Code
    Maximum Length: 30
    Long postal code for the location address. Long postal codes are used in some countries in addition to the short postal codes.
  • Title: Postal Code
    Maximum Length: 30
    Postal code for the location address.
  • Title: Provider
    Maximum Length: 150
    Company that has validated a location address.
  • Title: Region 1
    Maximum Length: 120
    Primary region in which the address is located. This value may be required depending on the country specified.
  • Title: Region 2
    Maximum Length: 120
    Secondary region withing the primary region.
  • Title: Region 3
    Maximum Length: 120
    Subregion within the secondary region.
  • Title: Time Zone Code
    Maximum Length: 50
    Code of the time zone.
  • Title: Town or City
    Maximum Length: 60
    Town or city of the location address. This value may be required depending on the country specified.
  • Title: Validation Status Code
    Maximum Length: 120
    Level of accuracy of a location address as determined by an address provider.
Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Body ()
Root Schema : locationsV2-addresses-item-response
Type: object
Show Source
Back to Top