Repository navigation
WebhookEvent knows email.scheduled, email.failed, email.suppressed and email.prefetched (0.10.0) - #19
Merged
Merged
Conversation
… (0.10.0) - EMAIL_SCHEDULED comes before EMAIL_SENT, and EMAIL_FAILED and EMAIL_SUPPRESSED right after EMAIL_COMPLAINED, in the server's order. They need MillionSend v0.15.1 or later; an older server answers 422 validation_error to a webhook naming them. - Docs: what each one means, data.failed.reason and data.suppressed, source_id on suppression.added and suppression.removed, and the v0.15.1 row under Server versions. suppression.* events are no longer called MillionSend extensions: Resend emits them too. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- EMAIL_PREFETCHED sits between EMAIL_CLICKED and EMAIL_RECEIVED, in the server's order. CreateWebhookOptions takes only WebhookEvent, so Java callers could not subscribe to it before. It is opt-in: an endpoint gets it only by naming it, never through all events. - README: the opt-in note for email.prefetched, and the metadata-only suppressed email an all-suppressed POST /emails keeps from v0.15.1 (each retry keeps another, even with the same Idempotency-Key). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
….15.1 row The server sets a suppression's source_id only when an SES bounce or complaint creates the entry; unsubscribes and entries added through the API carry null too, not only manual ones. The README's v0.15.1 row now names the suppressed email kept when the suppression list alone refuses a send, and the prefetched triggers read as examples. 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.
WebhookEventgainsEMAIL_SCHEDULED,EMAIL_FAILEDandEMAIL_SUPPRESSEDin the server's order, plus the opt-inEMAIL_PREFETCHED. Java callers couldn't subscribe toemail.prefetchedbefore, becauseCreateWebhookOptionstakes onlyWebhookEvent.suppression.added/removedare no longer labeled MillionSend extensions: Resend emits them too.Suppression.getSourceId()is documented as the email whose bounce or complaint created the entry, and null otherwise. Unsubscribes and API-added entries are null too.data,source_id, and thesuppressedemail kept when the suppression list alone refuses a send. It also gains a v0.15.1 row in "Server versions".pom.xmlandHttpClient.VERSIONare now 0.10.0.ParityTestcover the wire names both ways and the webhook create body.Lint and javadoc pass, and tests pass locally. After merge, tag
v0.10.0to publish (the release now builds a valid Central bundle, #18).🤖 Generated with Claude Code