Skip to main content

Observe Events

In this example, we will show you how to use the CreativeEditor SDK's CreativeEngine to subscribe to creation, update, and destruction events of design blocks.

Explore a full code sample on Stackblitz or view the code on Github.


This example uses the headless CreativeEngine. See the Setup article for a detailed guide. To get started right away, you can also access the block API within a running CE.SDK instance via cesdk.engine.block. Check out the APIs Overview to see that illustrated in more detail.

Subscribing to Events#

The event API provides a single function to subscribe to design block events. The types of events are:

  • 'Created': The design block was just created.

  • 'Updated': A property of the design block was updated.

  • 'Destroyed': The design block was destroyed. Note that a destroyed block will have become invalid and trying to use Block API functions on it will result in an exception. You can always use the Block API's isValid function to verify whether a block is valid before use.

All events that occur during an engine update are batched, deduplicated, and always delivered at the very end of the engine update. Deduplication means you will receive at most one 'Updated' event per block per subscription, even though there could potentially be multiple updates to a block during the engine update. To be clear, this also means the order of the event list provided to your event callback won't reflect the actual order of events within an engine update.

  • subscribe(blocks: number[], callback: (events: {type: string, block: number}[]) => void): () => void
    subscribe to events from a given list of blocks. Providing an empty list will subscribe to events from all of the engine's blocks. The provided callback will receive a list of events that occurred in the last engine update. Each event consists of the event type and the affected block. The returned function shall be used to unsubscribe from receiving further events.

Unsubscribing from events#

  • subscribe returns a function that can be called to unsubscribe from receiving events.

Note that it is important to unsubscribe when done. At the end of each update the engine has to prepare a list of events for each individual subscriber. Unsubscribing will help to reduce unnecessary work and improve performance.