NOT_FOUND
Find the correct Ovok route or resource after a not-found response.
HTTP 404. Problem type: https://docs.ovok.com/errors/not-found.
What this means
The requested route or resource could not be found. Some endpoints may also use this response when the caller cannot see a resource, so it does not always prove that the identifier is absent.
Troubleshooting
Check the base URL, route, version prefix, identifier, and active project or environment. Compare the path with the endpoint documentation and verify that the resource was created in the same context. If the identifier appears correct, ask an administrator to confirm your access rather than assuming the resource is safe to recreate.
Retry safely
Correct the route or identifier, or use the documented workflow to create a resource only after confirming that no existing resource should be used. Repeating the same lookup will not help if the path, project, or identifier is unchanged.
If the problem persists
Share the HTTP status, problem type, request path, response timestamp, and traceId with your administrator or support contact. Do not include access tokens or sensitive patient data. The Error responses guide explains the response fields and field-level errors.
Last updated on