Deletes sports inventory entities. Each object in the array must contain exactly one identifying key — do not send multiple key types in the same object.

Cascade scope — deleting a parent deletes its descendants: Category → Classes, Types, Events, Markets, Selections; Class → Types and below; Type → Events and below; Event → Markets and Selections; Market → Selections.

Safe parent-delete rule — send parent deletes individually (one Category, Class, Type, Event, or Market per request) when you rely on descendant cascading: batch optimisation can delete the named parents without applying the same immediate descendant cascade. Leaf Selection deletes may be batched freely.

Deleting a key that is already absent is effectively a no-op; the asynchronous acceptance response does not report whether a matching row existed. X-Expires-After is not accepted on DELETE.