UiPath Documentation
industry-department-solutions
latest
false
  • Overview
    • Introduction
    • Getting Started
    • API Guide
    • Customizations
    • Data Onboarding Checklist
  • API Resources
UiPath logo, featuring letters U and I in white

Supply Chain & Retail Solutions API guide

Last updated Apr 16, 2026

Location Extra

Overview

The Location Extra resource provides a flexible mechanism for storing additional, custom attributes against a location that are not captured in the core Locations schema. Each record represents a single key-value attribute pair for a location, enabling extensibility without schema changes.

Resource Endpoint

/api/v2/ingest/object/INV_LOCATION_EXTRA_OOTB
/api/v2/ingest/object/INV_LOCATION_EXTRA_OOTB

Supported Methods

MethodReturn TypeDescription
POSTResponseIngest (create/update) Location Extra records via UPSERT operation

Request Headers

HeaderRequiredDescription
AuthorizationYesYour Personal Access Token (PAT) from platform.peak.ai
Content-TypeYesMust be application/json

Properties

Primary Keys

  • location_id (string) - Unique identifier for the location this attribute belongs to. Part of the composite primary key.
  • location_extra_id (string) - Unique identifier for this specific extra attribute record. Part of the composite primary key.
  • updated_at (timestamp) - Timestamp of the most recent update to the record. Part of the composite primary key.

Attributes

AttributeData TypeRequiredDescription
location_idstringYesUnique identifier for the location this attribute belongs to
location_extra_idstringYesUnique identifier for this extra attribute record
location_extra_attributestringYesThe name of the custom attribute (e.g. "capacity_units", "region")
location_extra_valuestringNoThe value of the custom attribute (e.g. "10000", "North")
updated_attimestampYesTimestamp of the most recent update to this record
created_attimestampYesTimestamp when this extra attribute record was first created

Relationships

Outbound References

The location_extra resource does not reference any downstream resources as foreign keys.

Inbound References

The following resource is referenced by location_extra:

  • locationslocation_idlocations.location_id

JSON Representation

{
  "solutionName": "INV_OOTB",
  "data": [
    {
      "location_id": "LOC-001",
      "location_extra_id": "ATTR-001",
      "location_extra_attribute": "capacity_units",
      "location_extra_value": "10000",
      "updated_at": "2025-01-15 08:00:00",
      "created_at": "2025-01-10 08:00:00"
    }
  ],
  "operationType": "UPSERT"
}
{
  "solutionName": "INV_OOTB",
  "data": [
    {
      "location_id": "LOC-001",
      "location_extra_id": "ATTR-001",
      "location_extra_attribute": "capacity_units",
      "location_extra_value": "10000",
      "updated_at": "2025-01-15 08:00:00",
      "created_at": "2025-01-10 08:00:00"
    }
  ],
  "operationType": "UPSERT"
}

Example Request

curl -X POST \
  'https://service.peak.ai/ingestion-api/api/v2/ingest/object/INV_LOCATION_EXTRA_OOTB' \
  -H 'Authorization: YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "solutionName": "INV_OOTB",
    "data": [
      {
        "location_id": "LOC-001",
        "location_extra_id": "ATTR-001",
        "location_extra_attribute": "capacity_units",
        "location_extra_value": "10000",
        "updated_at": "2025-01-15 08:00:00",
        "created_at": "2025-01-10 08:00:00"
      }
    ],
    "operationType": "UPSERT"
  }'
curl -X POST \
  'https://service.peak.ai/ingestion-api/api/v2/ingest/object/INV_LOCATION_EXTRA_OOTB' \
  -H 'Authorization: YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "solutionName": "INV_OOTB",
    "data": [
      {
        "location_id": "LOC-001",
        "location_extra_id": "ATTR-001",
        "location_extra_attribute": "capacity_units",
        "location_extra_value": "10000",
        "updated_at": "2025-01-15 08:00:00",
        "created_at": "2025-01-10 08:00:00"
      }
    ],
    "operationType": "UPSERT"
  }'

Important Notes

  • location_id, location_extra_id, and updated_at together form the composite primary key. All three fields must be provided on every record.
  • location_extra_attribute is required and defines the name of the custom attribute being stored.
  • location_extra_value is optional; it may be omitted or set to null if no value is currently available for the attribute.
  • All attribute values are stored as strings, regardless of the underlying data type they represent.
  • location_id must correspond to an existing record in the Locations resource.
  • All timestamps must be provided in YYYY-MM-DD HH:MM:SS format.

Was this page helpful?

Connect

Need help? Support

Want to learn? UiPath Academy

Have questions? UiPath Forum

Stay updated