Repository navigation
Match MillionSend v0.15.1: email.scheduled, email.failed and email.suppressed (0.10.0) - #26
Merged
Merged
Conversation
…ppressed (0.10.0)
- WebhookEvent names email.scheduled (before email.sent), and
email.failed and email.suppressed (after email.complained), in the
API's order; the (string & {}) fallback stays.
- README: what the three carry (failed.reason; suppressed type, message
and reason), that endpoints subscribed to every event get them, and
source_id on suppression.added and suppression.removed.
- CHANGELOG: 0.9.0 dated 2026-10-16, its npm publish; 0.10.0 needs
MillionSend v0.15.1.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…suppressed record - WebhookEvent names email.prefetched right after email.clicked, as the API orders it, with a note that it reaches only endpoints that list it. - README: email.prefetched joins the subscribable events as opt-in. An emails.send the suppression list alone refuses keeps a metadata-only suppressed email that fires email.suppressed (MillionSend v0.15.1), one per retry even with the same idempotencyKey. - CHANGELOG 0.10.0: a bullet for email.prefetched; the README bullet and the v0.15.1 row name the kept suppressed email. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…0.15.1 row email.received moves next to email.prefetched, where the server lists it. The changelog row now matches the README: the suppressed email is kept only when the suppression list alone refuses the send. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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.
Matches MillionSend v0.15.1. Releases as 0.10.0.
WebhookEventnamesemail.scheduled,email.failedandemail.suppressedin the server's order. It also names the opt-inemail.prefetched(server v0.6.34+), which reaches only endpoints that list it.email.receivedmoves next to it, matching the server's order.data(failed.reason;suppressed.type,messageandreason, all open sets) and thesource_idonsuppression.added/suppression.removed. It also covers the metadata-onlysuppressedemail kept when the suppression list alone refuses anemails.send(each retry keeps another, even with the same idempotency key).package.jsonandSDK_VERSIONare now 0.10.0.Typecheck, lint, tests and build pass locally. After merge, tag
v0.10.0to publish.🤖 Generated with Claude Code