subscription.updated
Emitted whenever an existing subscription’s mutable state changes. Typical triggers include:- Status transition (e.g. PENDING -> ACTIVE, ACTIVE -> SUSPENDED)
- Product offering change completion
- Add-on modifications resulting in core attribute adjustments
- Port-in lifecycle progression impacting subscription state
- Metadata or configuration field updates
Payload
Standard event envelope plus latestSubscription
snapshot in data
.
Consumer guidance
- Compare fields to your stored version to derive a diff if you need change granularity
- Use the
occurredAt
timestamp for ordering heuristics (not a guaranteed total order) - De-duplicate using
type + occurredAt + data.id
(or hash of body)