Skip to content

feat(alerts): Add notify_on to alert thresholds - #426

Open
groyoh wants to merge 1 commit into
mainfrom
feat/alert-resolution
Open

groyoh wants to merge 1 commit into
mainfrom
feat/alert-resolution

Conversation

@groyoh

@groyoh groyoh commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

Context

The Alert Resolution feature in lago-api adds opt-in resolution notifications. Each alert threshold gains a notify_on array selecting which transitions it notifies on (triggered, and optionally resolved).

Description

notify_on, an optional list of strings, was added to the AlertThreshold request model and the AlertThresholdResponse response model. The wallet-alert fixture and client test cover the new field.

Depends on the OpenAPI contract in getlago/lago-openapi#585.

Part of ING-512.

## Context

The alert threshold contract gained a `notify_on` field, an array of
`triggered`/`resolved` that selects which transitions a threshold
notifies on. It applies to subscription and wallet alerts and is not
available on recurring thresholds.

## Description

`notify_on` was added to the `AlertThreshold` request model and the
`AlertThresholdResponse` response model. The wallet alert fixture and
test were updated to cover it.

The `alert.resolved` webhook event is not modeled: the Python client
does not model webhook payloads.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants