Get Location Profile
Returns one LocationProfile of one warehouse specified by the id and profile_id
path parameters. match is the latest intended definition — the pending revision’s
clauses while a rebuild is in flight, otherwise the published revision’s.
The response meta carries the warehouse-level membership repair freshness
(membership_status, membership_current, membership_repaired_at).
The match clauses keep selected Location Tags and Slot Types as compact {type, id}
references. For an editor, request fields=location_tags,slot_types together with
fields:location_tags=name,color and fields:slot_types=name,is_pickable to resolve
only those direct selections through included.
Authorizations
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
The id of the referenced Warehouse.
The id of the referenced LocationProfile.
Query Parameters
Specify additional fields of the LocationProfile object to be included in the response.
all, name, description, status, member_count, match, match_readable, location_tags, slot_types, active_revision, pending_revision, used_by, created_at, updated_at Specify fields of the directly referenced LocationTag objects to include under included.LocationTag. Add location_tags to the root fields parameter to return the relationship. type and id are always returned.
Specify additional fields of the LocationTag object to be included in the response.
basic, all, name, description, color, sort_order, is_deleted, created_at, updated_at Specify fields of the directly referenced SlotType objects to include under included.SlotType. Add slot_types to the root fields parameter to return the relationship. type and id are always returned.
Specify additional fields of the SlotType object to be included in the response.
basic, all, name, is_pickable, sort_order, patterns, is_fixed_capacity, slot_dimensions, weight_capacity, created_at, updated_at Response
A dictionary with a resource property that contains the requested
LocationProfile object.
A LocationProfile is a warehouse-scoped, named set of locations defined by match clauses
rather than by enumeration. Slotting Rules and Replenishment Policies target a profile
instead of listing locations, so the same policy keeps working as the warehouse grows.
Membership is materialized asynchronously. Saving a definition creates an immutable revision
and starts a build; the previously published revision keeps serving consumers until the
replacement is ready. A profile without a ready active revision has no resolved member set
and is never represented as an empty one — member_count is null rather than 0.
Direct Location Tags and Slot Types expanded through nested fields:* parameters.
Warehouse-level membership repair freshness. This is the freshness of the authoritative resolved membership, distinct from the Replenishment quantity computation freshness.