SupabaseS
Supabase•6mo ago
Alex

Twilio WA OTP Issue (Breaking)

Running into a WhatsApp OTP issue with Supabase’s Twilio integration. Our code explicitly sets "channel": "whatsapp":

response = supabase.auth.sign_in_with_otp(
    {
        "phone": "+13334445555",
        "options": { "channel": "whatsapp" },
    }
)


…but we’re still getting an SMS. If we hit Twilio’s Verify API directly via curl with the same credentials and parameters, the WhatsApp OTP comes through as expected:

curl -X POST "https://verify.twilio.com/v2/Services/$VERIFY_SERVICE_SID/Verifications" \
  --data-urlencode "To=$YOUR_PHONE_NUMBER" \
  --data-urlencode "Channel=whatsapp" \
  -u $TWILIO_ACCOUNT_SID:$TWILIO_AUTH_TOKEN


Our Supabase Auth provider is configured with the same service SID, auth token, etc. It looks like the SDK isn’t forwarding the channel parameter to Twilio. Can you confirm whether there’s a regression here? This is blocking our WA flows, really appreciate the help!
Was this page helpful?