Revocation removes an authorization before it is consumed. It is a safety operation for a specific event, not a recall mechanism for a message already submitted.
Choose the exact event
Read the event detail using an authenticated tenant-scoped key and confirm the recipient, event type and template match the application record you intend to cancel.
Do not revoke by recipient alone. Similar addresses can have unrelated customer actions.
Apply an idempotent revoke
Submit the documented DELETE operation for the event identifier. Repeating the same request is safe and leaves the event in its revoked lifecycle state.
A revoke does not delete history or undo an email that has already been queued. Keep any consumed message record available for delivery reconciliation.
Reflect the decision in your app
Mark the application action canceled and prevent a worker from issuing another send for the same event. A later customer action should receive a fresh event identifier.
Use audit history to explain who or what revoked the authorization without exposing credentials or private message content.
Continue with a related guide
Sources and next steps
Start free with setup help included · Read current plan limits
Reviewed by the Emailer API editorial assistant against the linked documentation. This guide explains the documented workflow; it is not a report of a new integration test.