Repository navigation
feat(alerting): Add subscriptions alerts API - #367
Merged
Merged
Conversation
vankiru
changed the base branch from
main
to
feat/move-wallets-api-to-customer-wallets
February 11, 2026 16:42
vankiru
changed the title
annvelents
reviewed
Feb 11, 2026
annvelents
left a comment
annvelents
left a comment
Contributor
There was a problem hiding this comment.
checked all the values for Alerts for both: you and me and updated my model to include values that you have. The only difference we have now is Alert vs AlertInput
vankiru
force-pushed
the
feat/add-subscriptions-alerts
branch
from
February 12, 2026 11:54
a45c8d2 to
3f12610
Compare
vankiru
marked this pull request as ready for review
February 12, 2026 12:05
vankiru
force-pushed
the
feat/move-wallets-api-to-customer-wallets
branch
from
February 17, 2026 09:49
6196069 to
f834aad
Compare
vankiru
force-pushed
the
feat/add-subscriptions-alerts
branch
from
February 17, 2026 10:14
3f12610 to
041ee4e
Compare
vankiru
force-pushed
the
feat/move-wallets-api-to-customer-wallets
branch
from
March 2, 2026 08:30
f834aad to
5c93b73
Compare
Base automatically changed from
feat/move-wallets-api-to-customer-wallets
to
main
March 2, 2026 09:05
vankiru
force-pushed
the
feat/add-subscriptions-alerts
branch
2 times, most recently
from
March 12, 2026 15:38
5a17cce to
043326e
Compare
vincent-pochet
force-pushed
the
feat/add-subscriptions-alerts
branch
from
October 27, 2026 16:07
043326e to
00cbb2d
Compare
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The API only finds active subscriptions unless subscription_status is given, so alerts of pending or terminated subscriptions were out of reach. The nested mixins now take an optional options query, and the subscription alerts client exposes subscription_status like the batch alert methods. The client also inherits the rate-limit settings of its parent, and the tests check the create and update payloads. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
vincent-pochet
force-pushed
the
feat/add-subscriptions-alerts
branch
from
October 27, 2026 16:35
d7d7654 to
6414b63
Compare
vincent-pochet
approved these changes
Oct 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
The client can only create or delete subscription alerts in batch (
create_alerts,delete_alerts). The API also exposes one alert at a time under/subscriptions/:external_id/alerts, which the client did not cover.Description
client.subscriptions.alerts, built on the nested command mixins like the wallet alerts client (feat(alerting): Add wallet alerts API #368).find_all(subscription_id, options=...)lists alerts,find(subscription_id, code)reads one.create(subscription_id, alert)creates one,update(subscription_id, code, alert)sends aPUT.destroy(subscription_id, code)deletes one.The batch methods on
SubscriptionClientare unchanged. Related API PR: getlago/lago-api#4925.🤖 Generated with Claude Code