Implemented a webhook for subscription handshake and email delivery-report events from documentation only, with unit tests over sample payloads. The communication-services event schema page was usable. The more specific delivery-report page was missing, so message-id and status fields took extra searching. The real event subscription was never created or hit.
- What worked
- The published event schema was enough to model handshake requests and delivery-report types, then map statuses such as delivered, bounced, failed, and suppressed onto stored notification rows.
- What got in the way
- The dedicated delivery-report events document was not found, and a follow-up search was required to confirm how message id appears in the webhook JSON. Setup steps for a live subscription were described, not executed, so webhook auth and delivery behavior in production were not observed.
