Webhooks
email.bounced
Sent when Amazon SES reports that the receiving server refused a message. The payload names the bounce as hard, soft or undetermined and carries the sub-type and the diagnostic code.
What the event tells you
A classification you can branch on
bounce_type is hard (permanent), soft (temporary) or undetermined.
The reason SES gives
bounce_sub_type and diagnostic_code carry the sub-type and the diagnostic text for the first bounced recipient.
Suppression follows the rule
A hard bounce suppresses the address at once. Soft and undetermined bounces suppress after 3 in 7 days.
Signed like every event
The request is signed with the endpoint's secret, so you can check where it came from.
Fields in data
- Common fields
- email_id, message_id, from, to, subject, status, tags, created_at.
- bounce_type
- hard, soft or undetermined.
- bounce_sub_type
- The SES sub-type, for example General, NoEmail or MailboxFull.
- diagnostic_code
- The receiving server's diagnostic text, when SES provides it.
- ses_bounce_type, timestamp, provider
- SES's own bounce type, its time for the bounce, and the provider, which is ses.
"bounce_type": "hard",
"bounce_sub_type": "General",
"diagnostic_code": "<text from the receiving server>",
"provider": "ses"PostFrame, answered
What is in the email.bounced payload?
The common fields (email_id, message_id, from, to, subject, status, tags, created_at) plus bounce_type, bounce_sub_type, ses_bounce_type, timestamp, diagnostic_code and provider.
How do I verify the request came from PostFrame?
Every request carries X-PostFrame-Signature (v1=<hex>) and X-PostFrame-Timestamp. Recompute HMAC-SHA256 over "<timestamp>.<body>" with the endpoint's signing secret, using the body exactly as received, and compare in constant time. The Node and Python snippets shown in the dashboard check this same scheme. The signing secret can be rotated through the API.
What happens if my endpoint is down?
PostFrame retries a failed delivery up to 4 times, waiting 10, 20, 40 and 80 seconds, and the endpoint's delivery log keeps one entry per delivery with the event type, last HTTP status, timing and attempt number. After the last attempt the event is not sent again. Each attempt times out after 10 seconds and redirects are not followed.
Can I try the endpoint before real traffic arrives?
Yes. Each endpoint has a Test action that sends a test event to your URL. Emails sent in test mode, for example with a pf_test_ API key, never dispatch webhooks.
Run your business from one place.
Five plans, 25 launch apps, one dashboard. Change tiers any time.
From $0 · Basic $9.95/mo · Upgrade or downgrade any time