Stock Movements record every change to inventory items such as when an order is received and allocated to a warehouse or a shipment is picked from the shelf.
Filters to apply to the request. Allowed properties for filtering: “id”, “entity_type”, “entity_action”, “entity_id”, “sku”, “created_at”, “warehouse_id”, “location”, “adjustment_reason_code”, “hold_reason_code”.hold_reason_code filters by the rolled-up parent reason code on movements attributed to a governing hold and accepts the standard filter operators. Movements without a governing hold have a null hold reason, so a null condition also matches those movements. This field is filter-only and cannot be used as a sort_field.
The code of the structured Adjustment Reason recorded when an inventory adjustment was made (for example, a cycle count or manual correction). Allowed values: “cycle_count”, “found”, “shrinkage”, “damaged”, “defective”, “expired”, “destroyed”, “receiving_error”, “shipping_error”, “customer_return”, “sample”, “other”.
The rolled-up parent reason code for the movement’s governing hold. User-defined reasons roll up to their parent system code (for example, a custom “Merchant Review” reason reports its parent “qc_inspection”). Null when the movement has no governing hold. Filterable through the hold_reason_code filter using the standard filter operators.
The internal parent hold ID, or null for a direct location hold. This can reference a lot-scope sentinel that has no stock movement row, so it provides partial relationship metadata and does not guarantee that the complete hold tree can be reconstructed from this endpoint.
The exact hold reason code applied. This is the child reason and can differ from the top-level hold_reason_code, which rolls up to the parent system code.
