SIGNALS CODE INVALID
Troubleshoot signals code invalid responses from the Ovok API.
HTTP 422. Stable Problem Details type: https://docs.ovok.com/errors/signals-code-invalid.
What this means
The vital-sign code is empty, malformed, too long, or contains unsupported characters. Clients should branch on type and status, not on human-readable detail text.
Troubleshooting
Use a supported threshold code, remove spaces and slashes, and avoid sending a display label or a list to a single-code route. Compare the request with the relevant endpoint's documentation and confirm the authenticated project and environment. Record the request path and traceId before escalating; the identifier lets an administrator find server-side context without sharing credentials or patient data.
Related endpoint guidance
The routes that answered this error were removed with Ovok's /v1/signals API. A new Signals API is being designed; see Working with Signals.
Retry safely
Correct the request, configuration, access or project state described above before retrying. Repeating an unchanged request will normally return the same error; for writes, check whether the first attempt changed state before sending it again. Follow endpoint-specific idempotency and concurrency guidance. Do not retry in a tight loop or use a broader permission or project setting to bypass the check.
If the problem persists
Share the HTTP status, problem type, request path, response timestamp, and traceId with your administrator or support contact. Remove access tokens, provider secrets, and sensitive patient data from the report. The Error responses guide explains the response fields, while the machine-code registry lists every endpoint-specific type audited for this release.
Last updated on