An audit trail should explain what the application asked for, which checks passed and what happened later. It should not become a second secret store.
Keep the customer action
Retain your own stable event identifier, customer record reference and intended recipient. The email API event record adds verification and template context for the same action.
Do not copy callback secrets, API keys or raw personal message content into analytics or public logs.
Record state transitions
Track event authorization, consumption, expiration and explicit revocation as separate states. A consumed event cannot be treated as a fresh send permission.
Record provider request IDs and safe error codes when available so support can reconcile a failure without printing credentials or full payloads.
Explain later outcomes
Delivery events describe transport observations after queue acceptance. Keep bounce, complaint, suppression and unavailable inbox-placement measurements distinct.
Use the detail endpoint for a specific event and apply tenant-scoped authentication. History is evidence for diagnosis, not proof of customer engagement.
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.