The platform's WhatsApp Cloud API integration gains authentication, observability and webhook coverage in this release, bringing outbound messaging in line with the audit expectations of the rest of the runtime.
Authentication templates and one-time passwords
- OTP button types. Authentication templates now build with the dedicated one-time-password buttons Meta requires — copy-code, one-tap and zero-tap — rather than the generic copy-code button, which Meta rejects on that category.
- Category-guarded builders. Each button is guarded to the template categories Meta accepts it on, so an invalid combination is caught when the template is defined rather than when it is submitted.
Audit logging and webhook coverage
- Outbound send audit log. Every send records an audit entry — recipient, message type, template or media, message id, status and any error — persisted to a dedicated log table that mirrors the existing mail-send log.
- Call and status events. The webhook parser now reads call status and call-termination fields alongside message status updates, mapping Meta's fields to typed enumerations.
- Template recategorization. A distinct webhook field for automatic or reviewed template recategorization is parsed, exposing the previous and new category for a completed or impending change.
The audit log skips silently when no user principal is available, so system-initiated sends do not fail for lack of an actor, and existing message-send calls continue to work unchanged.