Subscription hierarchy and deletion rules

Subscriptions are part of a system of interconnected components. Understanding this hierarchy helps you avoid configuration errors, manage dependencies, and plan what you can safely delete.

Component hierarchy [#component-hierarchy]

Subscriptions are the binding layer between two independent pools of resources: events and notification profiles.

• Events: Independent event types (DELIVERY, INBOUND_MESSAGE, CLICK, and others) that exist at the channel level. A subscription selects one or more events to listen for.
• Notification profiles: Reusable delivery configurations with a webhook URL and optional authentication settings or certificates. A subscription references exactly one profile.
• Subscriptions: Each subscription binds selected events to a notification profile, with optional filters to narrow which events trigger notifications. Multiple subscriptions can reference the same event types or share the same notification profile.

Deletion constraints [#deletion-constraints]

You can only delete a component if nothing else depends on it. Delete from the top of the hierarchy down: remove the dependent first (subscription), then the dependency (notification profile, authentication settings, certificate).

Deletion sequence example [#deletion-sequence]

To fully remove a subscription setup with all its components, delete top-down:

For component reuse patterns (shared vs independent setups), see Subscription components.

Best practices [#best-practices]

Plan component reuse

Decide upfront which components to share. This reduces configuration overhead and simplifies ongoing management.

Review dependencies before deleting

Before deleting a notification profile, check if other subscriptions depend on it. Reassign them to a different profile first.

Delete top-down

Delete subscriptions before profiles, profiles before authentication settings, and authentication settings before certificates.

Use clear naming

Name notification profiles and authentication settings descriptively so you can identify what each component does and what depends on it.