Delete a profile
Remove a practitioner's or clinic's public profile.
DELETE /v1/public-profiles/:profileIdDeletes the public profile. The practitioner keeps their Medos account, their appointments and their history — only the public-facing record goes.
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
profileId | number | Yes | The doctor's user id, or the workspace id. |
Unlike reading a profile, this
route takes no profileType.
Try it
/v1/public-profiles/:profileIdPath
DELETE /v1/public-profiles/https://api.medos.oneUse a dedicated test key, and put your browser's address on its allowlist
A Developer API key authenticates on its own, so it only works from the addresses registered against it — and this page calls from your browser, not your servers. Unless your own public address is on the list you get a 403 naming it, which is the allowlist doing its job. Your browser may also reach us over IPv6 even when your server does not, so the address in the error is often not the one you expected. The key here is kept in memory only and never written to storage, but create a test key for it and deactivate that key when you are done.
Request
curl -sX DELETE "https://api.medos.one/v1/public-profiles/4" \
-H "x-api-key: $MEDOS_API_KEY"Response
200 on success. Afterwards:
- Workspace detail returns
publicProfile: nullfor that doctor. They still appear indoctors[]and can still be booked — but with no name and no photograph, so make sure your rendering handles it. - Reading the profile returns
404.
Common failures
| Status | Cause |
|---|---|
403 | The profile belongs to another workspace. |
404 | No profile for that id. |
Consider unpublishing instead
Deletion discards the copy, the gallery and the FAQs. If the clinic only wants
the profile off the public site,
write it back with
isDraft=true — reversible, and nothing is lost.