Validate Incoming Requests

Twilio requires that your TwiML-serving web server be open to the public. This is necessary so that Twilio can retrieve TwiML from urls and POST data back to your server.

However, there may be people out there trying to spoof the Twilio service. Luckily, there’s an easy way to validate that incoming requests are from Twilio and Twilio alone.

An in-depth guide to our security features can be found in our online documentation.

Before you can validate requests, you’ll need four pieces of information:

  • your Twilio Auth Token (found in your Dashboard)
  • the POST data for the request
  • the requested URL
  • the X-Twilio-Signature header value

Obtaining the last three pieces of information depends on the framework you are using to process requests. The below example assumes that you have the POST data as a dictionary and the url and X-Twilio-Signature as strings.

The below example will print out a confirmation message if the request is actually from Twilio.

from twilio.util import RequestValidator


validator = RequestValidator(AUTH_TOKEN)

# the callback URL you provided to Twilio
url = ""

# the POST variables attached to the request (eg "From", "To")
post_vars = {}

# X-Twilio-Signature header value
signature = "HpS7PBa1Agvt4OtO+wZp75IuQa0=" # will look something like that

if validator.validate(url, post_vars, signature):
    print "Confirmed to have come from Twilio."
    print "NOT VALID.  It might have been spoofed!"

Trailing Slashes

If your URL uses an “index” page, such as index.php or index.html to handle the request, such as: where the real page is served from, then Apache or PHP may rewrite that URL a little bit so it’s got a trailing slash, such as for example.

Using the code above, or similar code in another language, you could end up with an incorrect hash because Twilio built the hash using and you may have built the hash using More information can be found in our documentation on validating requests.