Warehouses

A warehouse can be an actual warehouse, a store, or any type of stocking location or site that requires inventory tracking and management. Warehouse also serves as a dimension that can be set on transactions to expand report functionality and insight. See Define warehouses for more information.

List warehouses

get/objects/inventory-control/warehouse

Returns up to 100 object references from the collection with a key, ID, and link for each warehouse. This operation is mostly for use in testing; use query to find objects that meet certain criteria and to specify properties that are returned.

Permissions and other requirements
SubscriptionInventory Control
User ypeBusiness, CRM, Employee, Warehouse
PermissionsList, View Warehouses
SecurityOAuth2
Responses
200

OK

400

Bad Request

Request samples
Response samples
application/json
{
  • "ia::result": [
    • {
      • "key": "5",
      • "id": "103",
      • "href": "/objects/inventory-control/warehouse/5"
      },
    • {
      • "key": "8",
      • "id": "101",
      • "href": "/objects/inventory-control/warehouse/8"
      },
    • {
      • "key": "9",
      • "id": "100",
      • "href": "/objects/inventory-control/warehouse/9"
      }
    ],
  • "ia::meta": {
    • "totalCount": 3,
    • "start": 1,
    • "pageSize": 100
    }
}

Create a warehouse

post/objects/inventory-control/warehouse

Creates a new warehouse. For a warehouse hierarchy, create the parent warehouses before adding child warehouses.

Permissions and other requirements
SubscriptionInventory Control
User ypeBusiness
PermissionsList, View, Add Warehouses
SecurityOAuth2
Request
Request Body schema: application/json
id
required
string

Unique identifier for the warehouse.

Example: "USNA1"
name
required
string

Name of the warehouse.

Example: "US NA Warehouse-1"
required
object

The geographical location of the warehouse.

id
string
Example: "PHO--Phoenix"
key
string

System-assigned key for the location.

Example: "2"
status
string
Default: "active"

Object status. Active objects are fully functional. Inactive objects are essentially hidden and cannot be used or referenced.

Enum: "active" "inactive"
Example: "active"
isReplenishmentEnabled
boolean
Default: true

This property is set to true by default if Inventory Control is configured for replenishment. If the warehouse should not be replenished, set to false.

Example: true
enableNegativeInv
boolean
Default: false

Set to true to save transactions that cause the inventory for items in this warehouse to be negative.

Example: true
object

If this warehouse is part of a hierarchy, the parent warehouse of this warehouse.

id
string

Unique identifier for the parent warehouse.

Example: "WH10001--US AZ Warehouse 10001"
key
string

System-assigned key for the parent warehouse.

Example: "32"
object

Employee who is responsible for the warehouse.

id
string

Unique identifier of the employee who is the warehouse manager.

Example: "EM 1--Aman"
key
string

System-assigned key for the warehouse manager.

Example: "23"
object

The contact for the warehouse.

object
id
string

Name for the warehouse contact.

Example: "Sam Smith"
key
string

System-assigned key for the warehouse contact.

Example: "210"
object

Ship to contact for the warehouse.

id
string

Name for the Ship to contact.

Example: "Bill North"
key
string

System-assigned key for the Ship to contact.

Example: "223"
Responses
201

Created

400

Bad Request

Request samples
application/json
{
  • "id": "childId2",
  • "name": "child2",
  • "location": {
    • "id": "1--Chicago"
    },
  • "parent": {
    • "id": "101--Distribution Center"
    },
  • "manager": {
    • "id": "1--Courtney, Bill"
    },
  • "contacts": {
    • "primary": {
      • "id": "Sam Smith"
      },
    • "shipTo": {
      • "id": "Bill North"
      }
    },
  • "status": "active",
  • "isReplenishmentEnabled": true
}
Response samples
application/json
{
  • "ia::result": {
    • "key": "12",
    • "id": "103",
    • "href": "/objects/inventory-control/warehouse/12"
    },
  • "ia::meta": {
    • "totalCount": 1
    }
}

Get a warehouse

get/objects/inventory-control/warehouse/{key}

Returns detailed information for a specified warehouse.

Permissions and other requirements
SubscriptionInventory Control
User ypeBusiness, CRM, Employee, Warehouse
PermissionsList, View Warehouses
SecurityOAuth2
Request
path Parameters
key
required
string

System-assigned unique key for the warehouse.

Responses
200

OK

400

Bad Request

Request samples
Response samples
application/json
{
  • "ia::result": {
    • "key": "3",
    • "name": "US NA Warehouse-1",
    • "id": "USNAWA1",
    • "parent": {
      • "id": "US NA--1",
      • "key": "22",
      • "href": "/objects/inventory-control/warehouse/22"
      },
    • "location": {
      • "id": "North America--North America",
      • "key": "10",
      • "href": "/objects/company-config/location/10"
      },
    • "manager": {
      • "id": "EM 1--Aman",
      • "key": "14",
      • "href": "/objects/company-config/employee/14"
      },
    • "contacts": {
      • "primary": {
        },
      • "shipTo": {
        }
      },
    • "status": "active",
    • "isReplenishmentEnabled": true,
    • "enableNegativeInv": false,
    • "href": "/objects/inventory-control/warehouse/15",
    • "audit": {
      • "createdDateTime": "2021-04-21T23:57:50Z",
      • "modifiedDateTime": "2021-04-21T23:59:40Z",
      • "createdBy": "1",
      • "modifiedBy": "1"
      }
    },
  • "ia::meta": {
    • "totalCount": 1
    }
}

Update a warehouse

patch/objects/inventory-control/warehouse/{key}

Updates an existing warehouse by setting field values. Any fields not provided remain unchanged.

Permissions and other requirements
SubscriptionInventory Control
User ypeBusiness
PermissionsList, View, Edit Warehouses
SecurityOAuth2
Request
path Parameters
key
required
string

System-assigned unique key for the warehouse.

Request Body schema: application/json
name
string

Name of the warehouse.

Example: "US NA Warehouse-1"
status
string
Default: "active"

Object status. Active objects are fully functional. Inactive objects are essentially hidden and cannot be used or referenced.

Enum: "active" "inactive"
Example: "active"
isReplenishmentEnabled
boolean
Default: true

This property is set to true by default if Inventory Control is configured for replenishment. If the warehouse should not be replenished, set to false.

Example: true
enableNegativeInv
boolean
Default: false

Set to true to save transactions that cause the inventory for items in this warehouse to be negative.

Example: true
object

The geographical location of the warehouse.

id
string
Example: "PHO--Phoenix"
key
string

System-assigned key for the location.

Example: "2"
object

If this warehouse is part of a hierarchy, the parent warehouse of this warehouse.

id
string

Unique identifier for the parent warehouse.

Example: "WH10001--US AZ Warehouse 10001"
key
string

System-assigned key for the parent warehouse.

Example: "32"
object

Employee who is responsible for the warehouse.

id
string

Unique identifier of the employee who is the warehouse manager.

Example: "EM 1--Aman"
key
string

System-assigned key for the warehouse manager.

Example: "23"
object

The contact for the warehouse.

object
id
string

Name for the warehouse contact.

Example: "Sam Smith"
key
string

System-assigned key for the warehouse contact.

Example: "210"
object

Ship to contact for the warehouse.

id
string

Name for the Ship to contact.

Example: "Bill North"
key
string

System-assigned key for the Ship to contact.

Example: "223"
Responses
200

OK

400

Bad Request

Request samples
application/json
{
  • "manager": {
    • "id": "2--Lapus, Alan"
    }
}
Response samples
application/json
{
  • "ia::result": {
    • "key": "9",
    • "id": "US NA Warehouse-2",
    • "href": "/objects/inventory-control/warehouse/9"
    },
  • "ia::meta": {
    • "totalCount": 1
    }
}

Delete a warehouse

delete/objects/inventory-control/warehouse/{key}

Deletes a warehouse.

Permissions and other requirements
SubscriptionInventory Control
User ypeBusiness
PermissionsList, View, Delete Warehouses
SecurityOAuth2
Request
path Parameters
key
required
string

System-assigned unique key for the warehouse.

Responses
204

No Content

400

Bad Request

Request samples
Response samples
application/json
{
  • "ia::error": {
    • "code": "invalidRequest",
    • "message": "Malformed URL",
    • "supportId": "sQrM9%7EYdh5oDEWVb80mrn9xuHjoAAAABBQ",
    • "details": [
      • {
        }
      ]
    }
}

Query warehouses

post/services/core/query

Queries an object for filtered data.

SecurityOAuth2
Request
Request Body schema: application/json
object
string

Object type to query, in the form <application-name>/<object name>. For custom objects use platform-apps/nsp::<object-name>.

Example: "inventory-control/warehouse"
fields
Array of strings

List of fields to include in the response. Can be any combination of these:

  • The name of a field in the object that you are querying, such as id.

  • The name of a field in a related object, using the form relatedObjectName.fieldName, such as vendor.id.

  • The result of an aggregate function run against the values in the returned objects. Use the form function:fieldName, such as min:startDate to return the earliest starting date. Valid function names are:

    • count
    • avg
    • sum
    • min
    • max
  • The result of an aggregate function run against the values in related objects, using the form function:relatedObjectName.fieldName, such as max:vendor.creditLimit. The same functions are supported as for object fields.

Example: ["key","id","max:vendor.creditLimit"]
Array of equal (object) or not equal (object) or less than (object) or (less than or equal (object)) or greater than (object) or (greater than or equal (object)) or in (object) or not in (object) or between (object) or not between (object) or contains (object) or does not contain (object) or starts with (object) or does not start with (object) or ends with (object) or does not end with (object)

Filter conditions to select the objects to return based on their field values. You use operators and conditions to build your filter, such as {"$eq":{"status":"active"}} to select objects in which status is equal to "active".

Example: [{"$eq":{"status":"active"}},{"$gt":{"totalDue":"1000"}},{"$contains":{"name":"Acme"}}]
Array
Any of:

Field value must be equal to this specified value.

For date fields, you can use these macro values that are relative to the current date or the asOfDate in filterParameters, if set:

  • today
  • currentWeek
  • currentMonth
  • currentQuarter
  • currentYear
  • yesterday
  • lastWeek
  • priorMonth
  • priorQuarter
  • priorYear

These are most useful for queries that you want to save and use repeatedly, such as for views or reports. Just change the asOfDate each time to retrieve the same data set for different time periods.

For example, {"eq":{"postingDate":"priorYear"}}.

object

The field name and value to be compared with object values.

Example: {"status":"active"}
filterExpression
string
Default: "and"

Logical operators to apply when there are multiple filter conditions. The conditions in the filters array are implicitly numbered starting at 1. Supports and, or, and grouping with parentheses.

Shortcuts:

  • and by itself means that all conditions must be true.
  • or by itself means that at least one condition must be true.
Example: "(1 and 2) or 3"
object

Pre-defined filter options.

asOfDate
string <date>

The "as of" date to use with any relative date comparisons in filters. For example, if asOfDate is set to "2022-04-01" then priorMonth will be "03".

The current date is used if asOfDate is not set.

Example: "2022-04-01"
includeHierarchyFields
boolean
Default: false

Set to true to include hierarchical structure information with each object in the response.

Example: false
caseSensitiveComparison
boolean
Default: true

Queries are case-sensitive by default. Set to false to ignore case in a query.

Example: true
includePrivate
boolean
Default: false

By default, in a multi-entity company, queries from the top-level entity do not access data in private entities. Set includePrivate to true if you want to query data in private entities.

Example: false
Array of objects

Set the order of the results by specifying field names to sort by and whether they should be in ascending or descending order.

Example: [{"totalDue":"asc"},{"lastPaymentMadeDate":"desc"}]
Array
property name*
additional property
string
Enum: "asc" "desc"
start
integer

First record of the result set to include in the response.

Example: 1
size
integer

Number of records to include in the response.

Example: 100
Responses
200

OK

400

Bad Request

Request samples
application/json
{
  • "object": "inventory-control/warehouse",
  • "filters": [
    • {
      • "$eq": {
        }
      }
    ],
  • "fields": [
    • "key",
    • "id",
    • "name",
    • "href"
    ],
  • "orderBy": [
    • {
      • "id": "asc"
      }
    ]
}
Response samples
application/json
{
  • "ia::result": [
    • {
      • "key": "2",
      • "id": "Distribution",
      • "name": "Distribution center",
      • "href": "/objects/inventory-control/warehouse/2"
      },
    • {
      • "key": "1",
      • "id": "WS000",
      • "name": "Fulfillment center",
      • "href": "/objects/inventory-control/warehouse/1"
      },
    • {
      • "key": "4",
      • "id": "WS001",
      • "name": "Texas warehouse",
      • "href": "/objects/inventory-control/warehouse/4"
      },
    • {
      • "key": "5",
      • "id": "WS002",
      • "name": "CA warehouse",
      • "href": "/objects/inventory-control/warehouse/5"
      }
    ],
  • "ia::meta": {
    • "totalCount": 4,
    • "start": 1,
    • "pageSize": 100,
    • "next": null,
    • "previous": null
    }
}