Create reservation steal-from rule
Creates a new reservation steal-from rule.
Authorizations
JWT Authorization header using the Bearer scheme.
Query Parameters
limits which fields are returned in the response body
Body
Reservation Steal-From Rule contract (CAT-7911). Structurally identical to
Mozu.ProductAdmin.Contracts.ReservationRules.ReservationRule except it does not
have TimeFenceDays; instead it adds an explicit Mozu.ProductAdmin.Contracts.ReservationStealFromRules.ReservationStealFromRule.StartDate/Mozu.ProductAdmin.Contracts.ReservationStealFromRules.ReservationStealFromRule.EndDate
window during which the rule is enabled — the same effective-date-window concept used by
Discounts and Price Lists, not a reworded time fence. Fully independent of the sibling
Mozu.ProductAdmin.Contracts.ReservationStealForRules.ReservationStealForRule.
Referenced call-off-order rule codes. Max 1 entry.
Unique identifier. Auto-generated when omitted on create.
Referenced customer rule codes. Max 1 entry.
Optional description, max 500 chars.
Whether the rule is active. Defaults to true when omitted/null on create or update.
End of the rule's effective window. Null = never expires. Must be >= StartDate when both supplied.
Read-only. Computed server-side: true when the current UTC instant is inside the effective window (StartDate null/≤now AND EndDate null/≥now), false otherwise. A rule with no dates is always active. This reflects the effective window alone and does not incorporate the enabled flag.
Opaque JSON metadata. Passed through unchanged.
Display name. Required, max 200 chars.
Referenced product rules. Max 1 entry.
Priority rank, unique per master catalog within the tenant. Auto-assigned on create when omitted or ≤0. Rejected (not auto-assigned) on update when omitted or ≤0.
Optional tiebreaker attribute name used by the reservation-stealing engine when two candidates match. Max 50 chars.
Start of the rule's effective window. Null = no lower bound.
When true the rule applies to all sites; ValidSites is ignored. When false/omitted and ValidSites is also omitted, ValidSites auto-populates with the calling site from the request context (FR-022); the save is rejected if no site context is available.
Site IDs this rule applies to.
Response
OK
Reservation Steal-From Rule contract (CAT-7911). Structurally identical to
Mozu.ProductAdmin.Contracts.ReservationRules.ReservationRule except it does not
have TimeFenceDays; instead it adds an explicit Mozu.ProductAdmin.Contracts.ReservationStealFromRules.ReservationStealFromRule.StartDate/Mozu.ProductAdmin.Contracts.ReservationStealFromRules.ReservationStealFromRule.EndDate
window during which the rule is enabled — the same effective-date-window concept used by
Discounts and Price Lists, not a reworded time fence. Fully independent of the sibling
Mozu.ProductAdmin.Contracts.ReservationStealForRules.ReservationStealForRule.
Referenced call-off-order rule codes. Max 1 entry.
Unique identifier. Auto-generated when omitted on create.
Referenced customer rule codes. Max 1 entry.
Optional description, max 500 chars.
Whether the rule is active. Defaults to true when omitted/null on create or update.
End of the rule's effective window. Null = never expires. Must be >= StartDate when both supplied.
Read-only. Computed server-side: true when the current UTC instant is inside the effective window (StartDate null/≤now AND EndDate null/≥now), false otherwise. A rule with no dates is always active. This reflects the effective window alone and does not incorporate the enabled flag.
Opaque JSON metadata. Passed through unchanged.
Display name. Required, max 200 chars.
Referenced product rules. Max 1 entry.
Priority rank, unique per master catalog within the tenant. Auto-assigned on create when omitted or ≤0. Rejected (not auto-assigned) on update when omitted or ≤0.
Optional tiebreaker attribute name used by the reservation-stealing engine when two candidates match. Max 50 chars.
Start of the rule's effective window. Null = no lower bound.
When true the rule applies to all sites; ValidSites is ignored. When false/omitted and ValidSites is also omitted, ValidSites auto-populates with the calling site from the request context (FR-022); the save is rejected if no site context is available.
Site IDs this rule applies to.

