Document GET /messages/whatsapp/status

[salmanbshah]

Why?

GET /messages/whatsapp/status was implemented in MessagesController as whatsapp_status but absent from all specs. Customers using the WhatsApp channel have no documented way to check message delivery status, forcing them to rely on guesswork or internal support.

How?

Added GET /messages/whatsapp/status to the Unstable spec, modeled after the adjacent GET /messages/status endpoint. Requires a message_id query parameter and returns a new whatsapp_message_status schema with delivery state, timestamps, template name, and optional error details.

Decisions

• Unstable only: WhatsApp messaging is a newer channel still evolving; Unstable is the appropriate version tier.
• New schema: Unlike the data connectors gap, no existing schema could be reused — whatsapp_message_status needed its own definition to capture WhatsApp-specific fields (template_name, error object).

Implementation Plan

API Documentation Gap Plan

Confirmed Gaps (this PR covers gap #4)

#	Controller	Missing Endpoints	Spec Target
1	api/v3/data_connectors_controller.rb	GET /data_connectors/{id}	Unstable only
2	api/v3/fin_voice_controller.rb	GET /fin_voice/conversation/{conversation_id}	Unstable + v2.15
3	api/v3/conversation_parts_controller.rb	PUT /conversations/{conversation_id}/conversation_parts/{id}	Unstable only
4	api/v3/messages_controller.rb	GET /messages/whatsapp/status	Unstable only

Skipped (feature-flagged, not yet GA)

• fin/tasks_controller.rb — ai_answers_billing_feature
• fin/api_controller.rb — fin-agent-api
• procedures_controller.rb — ProcedureRuns::Constants::FEATURE_FLAG

_{Generated with Claude Code}