All requests to Twilio's REST API require you to authenticate. Twilio supports two forms of authentication:
usernameset to your AccountSid and the
passwordset to your AuthToken. Your AccountSid and AuthToken can be found on your Account Dashboard.
usernameset to the API Key's
passwordset to the API Key's
Both authentication methods use HTTP basic auth because it is well supported with web development tools. Most HTTP clients (including web-browsers) present a dialog or prompt for you to provide a username and password for HTTP basic auth. Most clients will also allow you to provide credentials in the URL itself. For example:
You can retrieve a representation of a resource by GETting its url. The easiest way to do this is to copy and paste a URL into your web browser's address bar.
Creating or updating a resource involves performing an HTTP PUT or HTTP POST to a resource URI. In the PUT or POST, you represent the properties of the object you wish to update as form urlencoded key/value pairs. Don't worry, this is already the way browsers encode POSTs by default. But be sure to set the HTTP Content-Type header to "application/x-www-form-urlencoded" for your requests if you are writing your own client.
To delete a resource make an HTTP DELETE request to the resource's URL. Not all Twilio REST API resources support DELETE.
Twilio's REST API uses HTTP GET, POST, PUT and DELETE methods. Since some HTTP clients do not support methods PUT and DELETE, you can simulate them via POST by appending the query string parameter _method (yes, underscore method) to a resource URL. Valid values are PUT and DELETE.
For example, if you want to perform a DELETE request on a particular phone number resource you could:
But if your client is only capable of GET and POST, then you could perform a POST with a _method query string variable to achieve the same result: