In this guide we'll cover how to secure your Django application by validating incoming requests to your Twilio webhooks are, in fact, from Twilio.
With a few lines of code, we'll write a custom decorator for our Django project that uses the Twilio Python SDK's validator utility. We can then use that decorator on our Django views which accept Twilio webhooks to confirm that incoming requests genuinely originated from Twilio.
Let's get started!
The Twilio Python SDK includes a RequestValidator
class we can use to validate incoming requests.
We could include our request validation code as part of our Django views, but this is a perfect opportunity to write a Python decorator. This way we can reuse our validation logic across all our views which accept incoming requests from Twilio.
Confirm incoming requests to your Django views are genuine with this custom decorator.
1from django.http import HttpResponse, HttpResponseForbidden2from functools import wraps3from twilio import twiml4from twilio.request_validator import RequestValidator56import os789def validate_twilio_request(f):10"""Validates that incoming requests genuinely originated from Twilio"""11@wraps(f)12def decorated_function(request, *args, **kwargs):13# Create an instance of the RequestValidator class14validator = RequestValidator(os.environ.get('TWILIO_AUTH_TOKEN'))1516# Validate the request using its URL, POST data,17# and X-TWILIO-SIGNATURE header18request_valid = validator.validate(19request.build_absolute_uri(),20request.POST,21request.META.get('HTTP_X_TWILIO_SIGNATURE', ''))2223# Continue processing the request if it's valid, return a 403 error if24# it's not25if request_valid:26return f(request, *args, **kwargs)27else:28return HttpResponseForbidden()29return decorated_function30
To validate an incoming request genuinely originated from Twilio, we first need to create an instance of the RequestValidator
class using our Twilio auth token. After that we call its validate
method, passing in the request's URL, payload, and the value of the request's X-TWILIO-SIGNATURE
header.
That method will return True if the request is valid or False if it isn't. Our decorator then either continues processing the view or returns a 403 HTTP response for inauthentic requests.
Now we're ready to apply our decorator to any view in our Django project that handles incoming requests from Twilio.
Apply a custom Twilio request validation decorator to a Django view used for Twilio webhooks.
1from django.http import HttpResponse2from django.views.decorators.csrf import csrf_exempt3from django.views.decorators.http import require_POST4from twilio.twiml.voice_response import VoiceResponse, MessagingResponse567@require_POST8@csrf_exempt9@validate_twilio_request10def incoming_call(request):11"""Twilio Voice URL - receives incoming calls from Twilio"""12# Create a new TwiML response13resp = VoiceResponse()1415# <Say> a message to the caller16from_number = request.POST['From']17body = """18Thanks for calling!1920Your phone number is {0}. I got your call because of Twilio's webhook.2122Goodbye!""".format(' '.join(from_number))23resp.say(body)2425# Return the TwiML26return HttpResponse(resp)272829@require_POST30@csrf_exempt31@validate_twilio_request32def incoming_message(request):33"""Twilio Messaging URL - receives incoming messages from Twilio"""34# Create a new TwiML response35resp = MessagingResponse()3637# <Message> a text back to the person who texted us38body = "Your text to me was {0} characters long. Webhooks are neat :)" \39.format(len(request.POST['Body']))40resp.message(body)4142# Return the TwiML43return HttpResponse(resp)44
To use the decorator with an existing view, just put @validate_twilio_request
above the view's definition. In this sample application, we use our decorator with two views: one that handles incoming phone calls and another that handles incoming text messages.
Note: If your Twilio webhook URLs start with https://
instead of http://
, your request validator may fail locally when you use Ngrok or in production if your stack terminates SSL connections upstream from your app. This is because the request URL that your Django application sees does not match the URL Twilio used to reach your application.
To fix this for local development with Ngrok, use http://
for your webhook instead of https://
. To fix this in your production app, your decorator will need to reconstruct the request's original URL using request headers like X-Original-Host
and X-Forwarded-Proto
, if available.
If you write tests for your Django views those tests may fail for views where you use your Twilio request validation decorator. Any requests your test suite sends to those views will fail the decorator's validation check.
To fix this problem we recommend adding an extra check in your decorator, like so, telling it to only reject incoming requests if your app is running in production.
Use this version of the custom Django decorator if you test your Django views.
1from django.conf import settings2from django.http import HttpResponseForbidden3from functools import wraps4from twilio.request_validator import RequestValidator56import os789def validate_twilio_request(f):10"""Validates that incoming requests genuinely originated from Twilio"""11@wraps(f)12def decorated_function(request, *args, **kwargs):13# Create an instance of the RequestValidator class14validator = RequestValidator(os.environ.get('TWILIO_AUTH_TOKEN'))1516# Validate the request using its URL, POST data,17# and X-TWILIO-SIGNATURE header18request_valid = validator.validate(19request.build_absolute_uri(),20request.POST,21request.META.get('HTTP_X_TWILIO_SIGNATURE', ''))2223# Continue processing the request if it's valid (or if DEBUG is True)24# and return a 403 error if it's not25if request_valid or settings.DEBUG:26return f(request, *args, **kwargs)27else:28return HttpResponseForbidden()29return decorated_function30
Validating requests to your Twilio webhooks is a great first step for securing your Twilio application. We recommend reading over our full security documentation for more advice on protecting your app, and the Anti-Fraud Developer's Guide in particular.
To learn more about securing your Django application in general, check out the official Django security docs.