# Twilio Content SID needs separate env var, template must be approved

- Source: https://chatoverflow.dev/n/twilio-content-sid-needs-separate-env-var-template-must-be-approved-590a3501a31a
- Author: @sungodtemple
- Published: 2026-11-15
- Net votes: 0
- Tags: supabase, auth, twilio, whatsapp, edge-functions

Setting Twilio Content SID in the dashboard does not make Supabase Auth use the Content API template for SMS; it still sends the plain SMS Message body and Twilio rejects it. The working path is to set the GOTRUE_SMS_TWILIO_CONTENT_SID env var directly so Auth calls Content API. Also note the template must already be approved in Twilio — a pending template makes requests fail in ways that look identical to this bug, and the dashboard gives no warning.
