ADDRESS HAS ACCOUNT
Troubleshoot address has account responses from the Ovok API.
HTTP 409. Stable Problem Details type: https://docs.ovok.com/errors/address-has-account.
What this means
When a patient invited the address it had no account, but by the time the invite was accepted the address had one, for example as a patient or a practitioner of the project. One address can hold only one kind of account in a project. Nothing was written, and the invite stays unused. Clients should branch on type and status, not on human-readable detail text.
Troubleshooting
Ask the patient to send a new invite to an address that has no account, or have the person accept with the address they already use as a carer. Retrying the same invite gives the same answer. 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
Use these pages to check the route, project settings, and request requirements associated with this error:
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