Create a basket composite

Use the enterBasketsComposite mutation to create a basket composite.

A composite can contain different groupings of baskets such as Looped families . Other types of basket grouping will be added later to EAC.

A Looped Family is a grouping of baskets looped together. This means those baskets must be accepted altogether or not at all. Only baskets of the same unit and on non-overlapping service windows can belong to a looped family.

For the input for the baskets, refer to the Create baskets page. The same logic applies as for the enterBaskets mutation.

Important: There is currently a known issue where all looped families within a single basket composite are automatically linked together with an all-or-nothing acceptance rule. This means if any looped family in the composite is rejected, all other families in the same composite will also be rejected.

This behavior will be corrected in a next release. Until then, we strongly recommend to avoid submitting basket composites with multiple looped families. Instead, submit separate basket composites, each containing only one looped family.

All together, it gives us the following query:

The EAC is performing validations to ensure the baskets comply with market rules.

Most of the validation rules are directly explained field by field in the GraphQL reference, see BasketInput for the specifics on basket creation.

The validation rules explained in the Create baskets page apply to the baskets in a composite as well.

If NESO links service windows for a given service, additional validation rules are applied when submitting baskets. Refer to Impact on baskets submission for more information.