Keep sending with SendPulse. Tatami reads its delivery events and shows you what bounced, what got blocked, and what to fix next.
No DNS changes. No rerouting mail. See the SendPulse setup.
SendPulse
Sending as usual
Event webhook
https://tatamimonitor.com/webhooks/sendpulse/a8f3b2c9
Tatami
Last hour
Outlook deferrals up 4x
451 4.7.650 · 198.51.100.24
Your mail keeps flowing through SendPulse. Tatami only reads the events it reports.
SendPulse reports delivery through SMTP webhooks for transactional mail and Email Service webhooks for campaigns. Tatami accepts both feeds as JSON arrays and keeps SMTP response codes, bounce classifications, and campaign identifiers with each outcome so your team can investigate why a recipient bounced or a campaign was delayed.
SendPulse emits hard_bounces and soft_bounces as distinct events. Tatami records permanent failures as bounced outcomes and temporary mailbox or quota problems as deferred, with the SMTP response text when SendPulse supplies it.
SMTP events include smtp_server_response, response code, and subcode. Inspect those fields alongside the recipient domain when deciding whether a failure is an invalid address or a policy rejection.
Campaign webhooks identify traffic with task_id. Tatami stores that value as campaign context so a bounce can be traced back to the SendPulse mailing that produced it.
Tatami explains each bounce, watches your IPs and domains, and tells your team when something breaks.
1,240 Outlook bounces since 9:00, all from 198.51.100.24.
Microsoft is blocking that IP. Gmail and Yahoo look normal.
Also works in Claude Code and Codex through mcp.tatamimonitor.com.
Google, Yahoo, and Microsoft signals for every IP and domain.
Outlook is bouncing mail from 198.51.100.24 with 550 5.7.1 S3150.
Also sent to
Discord
Email
Rules on bounces, blocklists, volume, and throttling.
One filtered link per customer.
Point the SendPulse webhook at Tatami. Your mail keeps sending the same way.
Add a SendPulse source to your Tatami project and copy its webhook URL. Name the source for the SMTP account or Email Service workspace you are connecting.
In SendPulse Account Settings, open the API tab and create a webhook using the Tatami URL. Enable delivered, not delivered, hard bounce, soft bounce, spam, and unsubscribe events. Email Service requires a webhook per event type; SMTP lets you select several events on one webhook.
Send a test message through SendPulse SMTP or a campaign and confirm a delivery or bounce event appears in Tatami. SendPulse batches events, so allow up to a minute for the first payload to arrive.
Detail depends on the fields your webhook sends. Opens and clicks are not needed.
Use SMTP webhooks for transactional mail and Email Service webhooks for campaigns. Both POST a JSON array to the same Tatami URL. SMTP events include recipient, message_id, and SMTP response fields. Email Service events use email and task_id. Create one Tatami source per SendPulse product if you want those streams separated.
Soft bounces become deferred outcomes. Hard bounces and undelivered events become bounced outcomes. Tatami skips opened, clicked, new subscriber, list deletion, and campaign status-update events so the monitoring view stays focused on delivery results.
No. A delivery event means the receiving mail server accepted the message. It does not confirm whether it reached the inbox or spam folder. Tatami monitors the delivery events you send, bounce reasons, and sender reputation to help you investigate deliverability issues; it does not measure inbox placement.
Providers are unlimited on every plan. Connect the rest of your email stack the same way.
PostShiba deliverability tool
Amazon SES deliverability tool
Customer.io deliverability tool
Smartico deliverability tool
Bento deliverability tool
$10 per million emails. First 100 IPs free. See pricing
Connect the webhook and watch your first SendPulse events arrive in minutes.