ProvelyProve that the recipient mail server rejected the email. The bounced level proves the bounced state on the email record and the email.bounced event. Use it when the intent is to confirm a rejection, for example before a suppression.
| Fact | Value |
|---|---|
| Contract id | resend.email.bounced |
| Version | 1.0.0 |
| Hash | 56703353a6dbfaf3 |
| Completion level | bounced |
| Publisher | Built and signed by Provely. |
| Certification | Generated draft |
| Skill | Resend 0.1.0 |
| Valid for provider API versions | 1.5.1 |
What is the intent?
Confirm that the email bounced.
What is the subject and the action?
| Member | Value |
|---|---|
| Subject type | resend.email |
| Canonical effect | message.send |
| Provider operation | POST /emails |
| Idempotency | idempotency_key through Idempotency-Key, retry is safe |
Which false successes give CONTRADICTED?
- duplicate side effect
- partial completion
- pre existing state
- wrong subject
The signed contract states the exact conditions, the evidence and the timing. The runtime reads them. The page states the promise.
Where do these rules come from?
resend.openapi#/paths/~1emails/post: resend.openapi, retrieved 2026-09-05resend.openapi#/components/schemas/Email/properties/last_event: resend.openapi, retrieved 2026-09-05resend.openapi#/webhooks/email.bounced: resend.openapi, retrieved 2026-09-05resend.openapi#/components/schemas/Email/properties/created_at: resend.openapi, retrieved 2026-09-05resend.docs.webhooks#webhooks/event-types/p4: resend.docs.webhooks, retrieved 2026-09-05resend.openapi#/components/schemas/OutboundEmailEventData/properties/email_id: resend.openapi, retrieved 2026-09-05
Can resend.email.bounced return VERIFIED from the action response alone?
No. The action response is E1, and an acknowledgement is never terminal success. The contract needs evidence of level E2 or higher from Resend.
What happens after the timeout?
The verdict is UNVERIFIABLE. The operation ends.