Skip to content

Add logic around domain reputation flow - #143

Open
odunayoogungbure-rgb wants to merge 1 commit into
mainfrom
feature/msd-15158-add-logic-around-domain-reputation-flow
Open

odunayoogungbure-rgb wants to merge 1 commit into
mainfrom
feature/msd-15158-add-logic-around-domain-reputation-flow

Conversation

@odunayoogungbure-rgb

@odunayoogungbure-rgb odunayoogungbure-rgb commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

resolves MSD-15158: Add logic around domain reputation flow

I used AI to generate parts of this PR

Yes

Changelist

  • Add domain and account reputation events

Risks

None

Performance impact

None

Security impact

None

How to QA

1. Create a webhook with the reputation events (API only — no UI)

MailerSend ms = new MailerSend();
ms.setToken("your_token");

Webhook webhook = ms.webhooks().builder()
    .name("Reputation webhook")
    .url("https://webhook.site/your-url")
    .enabled(true)
    .addEvent(WebhookEvents.DOMAIN_REPUTATION_CHANGED)
    .addEvent(WebhookEvents.ACCOUNT_REPUTATION_CHANGED)
    .createWebhook("domain_id");

Then in the app open Webhooks and click the new webhook.

  • Expect: the call succeeds, and the webhook shows domain.reputation_changed and account.reputation_changed as its events.
  • If broken: the builder throws a MailerSendException for an invalid event before calling the API.

Does not need QA:

  • Other webhook events and endpoints (unchanged)

How to release

  • Merge after mailersend/mailersend#8953 is deployed; the API rejects these events until then.
  • Release a new minor version as usual.

Screenshots, recordings

N/A

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@odunayoogungbure-rgb odunayoogungbure-rgb self-assigned this Sep 30, 2026
@odunayoogungbure-rgb
odunayoogungbure-rgb marked this pull request as ready for review September 30, 2026 15:16
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.

1 participant