INVALID SIGNATURE

HTTP 401. Stable Problem Details type: https://docs.ovok.com/errors/invalid-signature.

What this meansCopy Anchor Link

A wearable provider notification arrived without a valid signature or URL token, so Ovok ignored it. The answer carries WWW-Authenticate. Clients should branch on type and status, not on human-readable detail text.

TroubleshootingCopy Anchor Link

For Suunto, check that the webhookSecret saved in Ovok equals the notification secret in Suunto's portal. For Withings, the URL token changes when the client ID changes; patients then reconnect and are subscribed with the new URL. A notification Ovok refuses is not lost data: the daily sync still reads it. 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 guidanceCopy Anchor Link

Use these pages to check the route, project settings, and request requirements associated with this error:

• Webhook URLs
• Wearables webhooks

Retry safelyCopy Anchor Link

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 persistsCopy Anchor Link

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.