Errors
not-found
The resource does not exist, or it belongs to an organization you are not part of.
404 Not Found · Not found · type: https://docs.dlogify.com/errors/not-found
When it happens
- The ID does not exist or was deleted.
- The resource belongs to another organization. dlogify answers 404, never 403, so it does not reveal that the resource exists.
- The path itself does not exist (for example a typo, or a missing
/v1/prefix).
How to fix it
Check the ID and that you are signed in to an account that is a member of the resource's organization. List the parent resource (for example the project's tickets) to find valid IDs.
Example
HTTP/1.1 404 Not Found
Content-Type: application/problem+json{
"type": "https://docs.dlogify.com/errors/not-found",
"title": "Not found",
"status": 404,
"detail": "Resource not found.",
"instance": "req_01j…"
}