Skip to contentSkip to navigationSkip to topbar
Page tools
Useful for sharing or LLM
Accelerate development with AI

On this pageProducts used
Looking for more inspiration?Visit the
Error
Application error

20404: Not Found

Twilio API Documentation and Error CodesAPI

Description

description page anchor

This error occurs when you request a resource that Twilio cannot find. Common reasons include using an incorrect or deleted SID, sending a malformed request path, using the wrong resource name or casing, or sending the request to the wrong product base URL.

Possible causes

possible-causes page anchor
  • The SID in the request does not exist, or the resource existed previously and has since been deleted.
  • A Verify Verification SID was approved or expired and then soft deleted. After that happens, requests to that Verification resource return 20404.
  • The request path points to a resource that does not exist, such as using TwilioCalls instead of Calls, or the path uses the wrong casing.
  • A required SID is missing or empty in the request path, which produces a malformed URL.
  • The request was sent to the wrong host or base URL for the product you are calling. Core REST API resources use https://api.twilio.com/2010-04-01. Verify uses https://verify.twilio.com/v2/.
  • You requested /Numbers/AvailableNumbers or another incorrect path for the Available Phone Numbers API. The correct resource path includes the country code and number type.
  • Use the exact SID returned by the resource create or list response, and send the request to the documented endpoint for that resource. For example, Call resources use /Accounts/{AccountSid}/Calls/{Sid}.json, and Verify fetches use /Services/{ServiceSid}/Verifications/{Sid}.
  • For Verify, do not fetch a Verification resource after it has been approved or expired. Use the Verification Check endpoint to validate the code, or start a new verification if you need a new verification attempt.
  • Match the resource name and path casing exactly as documented. Use Calls, not TwilioCalls or calls.
  • Validate every path value before sending the request. Ensure AccountSid, ServiceSid, CallSid, and VerificationSid values are present and non-empty.
  • Use the correct product host and base URL for the endpoint you are calling. Do not send core REST API requests to https://twilio.com or https://www.twilio.com.
  • To search for available phone numbers, use /AvailablePhoneNumbers/{CountryCode}/{Type}.json (for example, /AvailablePhoneNumbers/US/Local.json). See the AvailablePhoneNumber resource for the full endpoint reference.

Additional resources

additional-resources page anchor