Skip to main content
PUT
Update Handling Class

Authorizations

Authorization
string
header
required

Generate a JWT access token through a Custom Global Integration and provide it with each request in the Authorization header prefixed with "Bearer" and then a single space.

Path Parameters

id
integer<int32>
required

Handling Class ID.

Required range: x >= 1
Example:

14

Body

application/json
name
string

Human-readable Handling Class name.

Required string length: 1 - 255
Example:

"Heavy and Oversized"

sort_order
integer

Evaluation precedence within every selected Warehouse.

Required range: 0 <= x <= 1000000
Example:

25

warehouses
(WarehouseRef · object | null)[]

Complete replacement Warehouse set. An empty array is never accepted: a class emptied by a Warehouse deletion must be given a new Warehouse set here, or be deleted.

Minimum array length: 1

A reference to a Warehouse by id.

conditions
object

A one-level OR-of-AND condition tree. The server accepts the {"and": [...]} shorthand for a single group and always returns the canonical {"or": [{"and": [...]}]} form.

OpenAPI validates the structural envelope. ShipStream remains authoritative for available Product fields, field/operator compatibility, option values, measurement units, raw CEL validity, normalization, the limit of 64 condition rows across all groups, and the 65,535-byte compiled-expression limit. Editor clients can load the applicable Product field catalogue from GET /api/global/v1/inventory/product-profiles/condition-fields or GET /api/global/v1/inventory/handling-classes/condition-fields.

Example:

Response

OK - The operation completed successfully and there is no response body.