not_found
Generic resource-not-found when no module-specific error code applies.
not_found is the generic not-found sentinel used when a resource lookup fails and no more specific module-level code (e.g., calls.not_found, numbers.not_found) is defined for the endpoint. Most endpoints use module-specific codes; this generic form is a fallback.
The requested resource does not exist at the given URL, or the URL pattern does not match any registered route. If you expected a module-specific code, check whether the endpoint has a specific not-found code.
Verify the URL, resource ID, and workspace context. If the resource genuinely does not exist, no retry will resolve it.
{
"error": {
"code": "not_found",
"message": "resource not found",
"request_id": "req_01900000abc"
}
}