location.update

Update a Location entity to modify details about a location.

POST http://api.kompliant.com/location.update (OpenAPI specification)

Usage Info

The Location entity stores comprehensive information about location, including location type, name, owner details and address details. This entity can be associated with businesses as BusinessLocation or used independently within a Subject Record. Use this method if you want to change or add more information for an existing location.

Request

Authentication: KSig1-HMAC-SHA256

Parameters

ParameterTypeRequiredDescription
location_idstringYesThe identifier of a Location entity to modify.
locationobjectNoThe location parameter is defined in the table below.

Location Parameters

ParameterTypeRequiredNullableDescription
location_typeenumNoYesThe type of the location. Must be one of LOCATION_TYPES .
location_namestringNoYesThe name of a location.
owner_typeenumNoYesThe type of location owner. Must be one of LOCATION_OWNER_TYPES .
owner_namestringNoYesThe name of an owner of a location.
addressobjectNoyesThe address details for a location. The address parameter is defined in the table below.

Address Parameters

ParameterTypeRequiredDescription
line1stringNoPrimary street address information (building number, street name).
line2stringNoSecondary address information (apartment, suite, unit, etc.)
citystringNoCity or municipality name
statestringNoTwo character code for the state. Must be one of the STATES.
postal_codestringNoZIP or postal code for mail delivery
countrystringNoTwo character code for the country where the address is located. Must be one of the COUNTRIES.

Example

{
  "location_id": "l_57WfSCnafMnxDiWMKcy3EW",
  "location": {
    "location_type": "PROPERTY",
    "location_name": "Lake House",
    "owner_type": "BUSINESS",
    "owner_name": "Mark Johnson",
    "address": {
      "line1": "123 Maple Avenue",
      "line2": "Apartment 4B",
      "city": "Portland",
      "state": "OR",
      "postal_code": "97204",
      "country": "US"
    }
  }
}

Response

Data

An empty data object is returned when the completion is successful.

Example

{
  "meta": {
    "status": "SUCCESS",
    "trace_id": "trc_6zNzQZHSf26V83BO3uW6dS",
    "version": "2025-03-24"
  },
  "data": {}
}

Errors

Error CodeHTTP CodePossible Cause
BAD_REQUEST400Required parameters not provided.
Enum value provided does not correspond to an available type.
ENTITY_NOT_FOUND400The location_id provided does not exist.
ACCOUNT_CONFIGURATION_VIOLATION400Account configuration rule violations are described below.

ACCOUNT_CONFIGURATION_VIOLATION

When a ACCOUNT_CONFIGURATION_VIOLATION error occurs, the response will include additional entity_type and sub_code fields to provide more specific information:

Entity TypeSub-codeDescription
LocationFEATURE_NOT_ENABLEDLocation feature is not enabled for this account.