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

    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.

• Using a processing region that does not support selected service. For example, making requests to https://api.jp1.twilio.com/v1/SomeService will return a 404 indicating that SomeService is not currently supported in jp1.

Selected resource not available

Modify request to use a different service, path, user, or processing realm