404: Not Found
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.
- The
SIDin 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
SIDis 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
SIDdirectly 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
AccountSidand the target resourceSIDare present and non-empty. - Send the request to the correct product host and base URL for the endpoint you are calling.