industry-department-solutions
latest
false
- Overview
- API Resources

Supply Chain & Retail Solutions API guide
Last updated Apr 16, 2026
Locations
Overview
The Locations resource represents physical or logical nodes in the supply chain network, such as distribution centres, retail stores, and factories. Each location record captures the site's identity, geographic context, and its functional role within the inventory management system.
Resource Endpoint
/api/v2/ingest/object/INV_LOCATIONS_OOTB
/api/v2/ingest/object/INV_LOCATIONS_OOTB
Supported Methods
| Method | Return Type | Description |
|---|---|---|
| POST | Response | Ingest (create/update) Locations records via UPSERT operation |
Request Headers
| Header | Required | Description |
|---|---|---|
Authorization | Yes | Your Personal Access Token (PAT) from platform.peak.ai |
Content-Type | Yes | Must be application/json |
Properties
Primary Keys
- location_id (string) - Unique identifier for the location. Used as the primary key for deduplication and UPSERT operations.
- updated_at (timestamp) - Timestamp of the most recent update to the record. Combined with
location_idto form the composite primary key.
Attributes
| Attribute | Data Type | Required | Description |
|---|---|---|---|
location_id | string | Yes | Unique identifier for the location |
location_name | string | No | Human-readable name of the location (e.g. "Central Warehouse") |
country | string | No | Country in which the location resides |
is_store | boolean | Yes | Indicates whether the location is a retail store |
is_dc | boolean | Yes | Indicates whether the location is a distribution centre |
is_factory | boolean | Yes | Indicates whether the location is a manufacturing facility |
updated_at | timestamp | Yes | Timestamp of the most recent update to this record |
Relationships
Outbound References
The locations resource does not reference any other resource as a foreign key.
Inbound References
The following resources reference locations via location_id:
- stock —
location_id→locations.location_id - pricing —
location_id→locations.location_id - order_parameters —
location_id→locations.location_id - purchase_orders —
location_id→locations.location_id - transfers —
location_id→locations.location_id - manufacturing_orders —
location_id→locations.location_id - production_lines —
location_id→locations.location_id - sku_calendar —
location_id→locations.location_id - sales —
location_id→locations.location_id - customer_orders —
location_id→locations.location_id - location_extra —
location_id→locations.location_id
JSON Representation
{
"solutionName": "INV_OOTB",
"data": [
{
"location_id": "LOC-001",
"location_name": "Central Warehouse",
"country": "United Kingdom",
"is_store": false,
"is_dc": true,
"is_factory": false,
"updated_at": "2025-01-15 08:00:00"
}
],
"operationType": "UPSERT"
}
{
"solutionName": "INV_OOTB",
"data": [
{
"location_id": "LOC-001",
"location_name": "Central Warehouse",
"country": "United Kingdom",
"is_store": false,
"is_dc": true,
"is_factory": false,
"updated_at": "2025-01-15 08:00:00"
}
],
"operationType": "UPSERT"
}
Example Request
curl -X POST \
'https://service.peak.ai/ingestion-api/api/v2/ingest/object/INV_LOCATIONS_OOTB' \
-H 'Authorization: YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
"solutionName": "INV_OOTB",
"data": [
{
"location_id": "LOC-001",
"location_name": "Central Warehouse",
"country": "United Kingdom",
"is_store": false,
"is_dc": true,
"is_factory": false,
"updated_at": "2025-01-15 08:00:00"
}
],
"operationType": "UPSERT"
}'
curl -X POST \
'https://service.peak.ai/ingestion-api/api/v2/ingest/object/INV_LOCATIONS_OOTB' \
-H 'Authorization: YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
"solutionName": "INV_OOTB",
"data": [
{
"location_id": "LOC-001",
"location_name": "Central Warehouse",
"country": "United Kingdom",
"is_store": false,
"is_dc": true,
"is_factory": false,
"updated_at": "2025-01-15 08:00:00"
}
],
"operationType": "UPSERT"
}'
Important Notes
location_idandupdated_attogether form the composite primary key. Both fields must be provided on every record.- The boolean flags
is_store,is_dc, andis_factoryare all required. A location may have more than one flag set totrueif it serves multiple roles. - Timestamps must be provided in
YYYY-MM-DD HH:MM:SSformat. - Records are ingested via UPSERT: an existing record with matching primary keys will be updated; otherwise a new record is inserted.