OSS-first docs

These docs teach the open system first: contracts, generated surfaces, runtimes, governance, and incremental adoption. Studio shows up as the operating layer on top, not as the source of truth.

WhatsApp Meta

Meta WhatsApp is the primary WhatsApp channel for ContractSpec's messaging runtime, with signed webhook verification and reliable outbound delivery.

Required secrets and config

// secret payload
{
  "accessToken": "...",
  "appSecret": "...",
  "verifyToken": "..."
}

// required connection config
{
  "phoneNumberId": "120000000001",
  "apiVersion": "v22.0"
}

Webhook endpoints

  • Verification challenge: GET /webhooks/whatsapp/meta
  • Inbound messages: POST /webhooks/whatsapp/meta
  • Signatures are validated with x-hub-signature-256.

Workspace mapping

CHANNEL_WORKSPACE_MAP_WHATSAPP_META={"120000000001":"workspace-acme"}

Best practices

  • Keep verify and app secrets separate from access tokens.
  • Map each phone number ID to a workspace for strict tenant routing.
  • Use Twilio WhatsApp only as fallback when you need active-passive routing.