ProvelyProve that the receiving server denied the message permanently. A bounce event with the type bounce states it. A block states the type blocked, and a block never satisfies this level.
| Fact | Value |
|---|---|
| Contract id | sendgrid.email.bounced |
| Version | 1.0.0 |
| Hash | 1100fbbefd59997c |
| Completion level | bounced |
| Publisher | Built and signed by Provely. |
| Certification | Provisional |
| Skill | Twilio SendGrid Mail API 0.1.0 |
| Valid for provider API versions | v3 |
What is the intent?
Confirm that the message bounced.
What is the subject and the action?
| Member | Value |
|---|---|
| Subject type | sendgrid.message |
| Canonical effect | messaging.email_send |
| Provider operation | POST /v3/mail/send |
| Idempotency | none, retry is not safe |
Which false successes give CONTRADICTED?
- duplicate side effect
- 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?
sendgrid.openapi#/paths/~1v3~1mail~1send/post: sendgrid.openapi, retrieved 2026-09-08sendgrid.docs.events#event-webhook/the-bounce-event/p1: sendgrid.docs.events, retrieved 2026-09-08sendgrid.events#/events/bounce: sendgrid.events, retrieved 2026-09-08sendgrid.docs.events#event-webhook/custom-arguments/p1: sendgrid.docs.events, retrieved 2026-09-08sendgrid.docs.events#event-webhook/the-event-time/p1: sendgrid.docs.events, retrieved 2026-09-08sendgrid.docs.events#event-webhook/the-properties-of-a-delivery-event/p1: sendgrid.docs.events, retrieved 2026-09-08
Can sendgrid.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 E3 or higher from Twilio SendGrid Mail API.
What happens after the timeout?
The verdict is UNVERIFIABLE. The operation goes to a person for review.