business.getLocation
Retrieve a comprehensive details of a Business Location entity.
POST http://api.kompliant.com/business.getLocation (OpenAPI specification)
Usage Info
Retrieve comprehensive details of a Business Location entity including the Location entity associated with the Business.
Request
Authentication: KSig1-HMAC-SHA256
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| business_location_id | string | Yes | The identifier for the Business Location entity. |
| show_sensitive_data | boolean | No | A boolean value that if true, indicates that sensitive data should shown. If the parameter is not provided, the value defaults to false and the sensitive data will be masked.The sensitive data for the business_location is dependent on the sub entity Location. |
| verbose | boolean | No | A boolean value that when true includes the sub entities of the subject record in the response.The sub entity is Location. |
Example
{
"business_location_id": "bl_7eobHllxknr7mfqbjnX2Pp",
"show_sensitive_data": true,
"verbose": true
}
Response
Data
| Parameter | Type | Description |
|---|---|---|
| business_location | object | The business location object that contain information about Business Location associated with the Business. The Business Location object parameter is defined in the tables below. |
Business Location Parameters
| Parameter | Type | Description |
|---|---|---|
| business_location_id | string | The ID of the Business Owner. |
| location_id | string | The Person that is an owner of business. |
| created_at | string | The date-time when the Business Location was created. The value will be in ISO 8601 date and time format (YYYY-MM-DDTHH:mm:ss.SSSZ). |
| updated_at | string | The date-time when the Business Location was last updated. If there has been no update, the value will be the same as the created_at value. The value will be in ISO 8601 date and time format (YYYY-MM-DDTHH:mm:ss.SSSZ). |
| location | string | The location info parameter is defined in the table below. Requires verbose to be true to be displayed. |
Location Parameters
| Parameter | Type | Description |
|---|---|---|
| location_id | string | The identifier of the Location entity. |
| location_type | string | The type of the location. Must be one of the LOCATION_TYPES . |
| location_name | string | The name of the location. |
| owner_type | string | The type of the owner for a location. Must be one of the LOCATION_OWNER_TYPES . |
| owner_name | string | The name of the owner for a location. |
| address | object | The address details for a location. The address parameter is defined in the table below. |
| created_at | string | The date-time when the Location was created. The value will be in ISO 8601 date and time format (YYYY-MM-DDTHH:mm:ss.SSSZ). |
| updated_at | string | The date-time when the Location was last updated. If there has been no update, the value will be the same as the created_at value. The value will be in ISO 8601 date and time format (YYYY-MM-DDTHH:mm:ss.SSSZ). |
Example
{
"meta": {
"status": "SUCCESS",
"trace_id": "trc_2h1MG0xRq9dPAPWLuygFk5",
"version": "2025-03-24"
},
"data": {
"business_location": {
"business_location_id": "bl_5nCWRq51h3ILIJvOOhfF4i",
"location_id": "l_4PYsekjAX8VMuAOfmW81C7",
"created_at": "2025-01-17T22:45:38.206Z",
"updated_at": "2025-01-17T22:45:38.206Z",
}
}
}
Example with verbose
{
"meta": {
"status": "SUCCESS",
"trace_id": "trc_2h1MG0xRq9dPAPWLuygFk5",
"version": "2025-03-24"
},
"data": {
"business_location": {
"business_location_id": "bl_5nCWRq51h3ILIJvOOhfF4i",
"location_id": "l_4PYsekjAX8VMuAOfmW81C7",
"created_at": "2025-01-17T22:45:38.206Z",
"updated_at": "2025-01-17T22:45:38.206Z",
"location": {
"location_id": "l_4PYsekjAX8VMuAOfmW81C7",
"location_type": "PROPERTY",
"location_name": "Lake House Property",
"owner_type": "BUSINESS",
"owner_name": "Mark Johnson",
"address": {
"type": "PRIMARY_RESIDENCE",
"line1": "123 Maple Avenue",
"line2": "Apartment 4B",
"city": "Portland",
"state": "OR",
"postal_code": "97204",
"country": "US"
},
"created_at": "2025-01-18T14:22:55.109Z",
"updated_at": "2025-01-18T14:22:55.109Z"
}
}
}
}
Errors
| Error Code | HTTP Code | Possible Cause |
|---|---|---|
| BAD_REQUEST | 400 | Required parameters not provided. Invalid values provided. |
| ENTITY_NOT_FOUND | 400 | The business_location_id provided does not exist. |
| ACCOUNT_CONFIGURATION_VIOLATION | 400 | Account 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 Type | Sub-code | Description |
|---|---|---|
| Location | FEATURE_NOT_ENABLED | Location feature is not enabled for this account. |
Updated 6 months ago