Skip to contentSkip to navigationSkip to topbar
Page toolsOn this page
Looking for more inspiration?Visit the

404: Not Found


ERROR: 404

error-404 page anchor
ERROR

Twilio returns this error when it cannot find the resource in your request. This usually happens when the requested resource does not exist, the resource SID is incorrect or deleted, the request path is malformed, the resource name or casing does not match the documented endpoint, or the request was sent to the wrong product host.

Possible causes

possible-causes page anchor
  • The SID in the request does not exist, or the resource existed previously and has since been deleted.
  • The request path points to a resource that does not exist.
  • The request path uses the wrong resource name or casing.
  • A required SID is missing or empty in the request path.
  • The request was sent to the wrong host or base URL for the API you are calling.
  • Copy the SID directly from the resource create or list response, then retry the request with the documented endpoint for that resource.
  • Confirm that the resource still exists before you fetch, update, or delete it.
  • Match the documented resource name and path casing exactly.
  • Validate every path value before you send the request. Ensure required values such as AccountSid and the target resource SID are present and non-empty.
  • Send the request to the correct product host and base URL for the endpoint you are calling.

Additional resources

additional-resources page anchor