20404: Not Found

The resource was not found. Here are some examples of cases that may trigger a 404 error.

• Requesting a resource for a sid that does not exist, for example

  Copy code block

  1
    GET verify.twilio.com/v2/Services/VA123/VE123
  2
    Or 
  3
    POST verify.twilio.com/v2/Services/VA123/VerificationCheck
  4
  
  5
         1. The resource has never existed (incorrect SID).
  6
         2. The resource existed but has been deleted.
  7
         3. The resource is a Verification SID that has been "soft deleted" after the 
  8
             verification process is completed or expired. When a verification is 
  9
             approved or expires, Twilio performs a "soft delete" on the verification 
  10
             record. This means that while the record is no longer active and cannot 
  11
             be retrieved through the API, it is still stored in Twilio's system for 
  12
             compliance and auditing purposes. As a result, any subsequent 
  13
             requests to the Verification SID's REST API resource will return a 20404 
  14
             error, indicating that the resource is not found. 
  15
  
  16
    GET /2010-04-01/Accounts/AC123/Calls/CA123

  where CA123 is not a call sid that exists for your account

• Trying to retrieve a resource that doesn't exist, for example

  Copy code block

    GET /2010-04-01/Accounts/AC123/TwilioCalls/CA123

  where the resource name is Calls, not TwilioCalls. Note that the API is case sensitive, so requesting "calls" instead of "Calls" will also return a 404.

• Missing a sid in the request path. For example, let's say I accidentally don't set a value for a call sid, using the PHP helper library:

  Copy code block

  1
    $callSid = null;
  2
    $client->account->calls->get($callSid);

  This may turn into

  Copy code block

    GET /2010-04-01/Accounts/AC123/Calls/.json

  because of the nonexistent sid, which may 404 your request or give you back a result you were not expecting. Or, you may initialize the client with an empty string for an account sid, which means the URL will get truncated in the middle (note the consecutive slashes):

  Copy code block

    GET /2010-04-01/Accounts//Calls/CA123.json

• Using a base URL that is not https://api.twilio.com. For example, making requests to https://twilio.com or https://www.twilio.com will not work.