---
title: "Remove VetsGPT patient context"
method: DELETE
path: "/workspaces/{workspaceId}/vetsgpt/chats/{chatId}/attachments/patient"
tags: ["vetsgpt"]
---

# Remove VetsGPT patient context

`DELETE /workspaces/{workspaceId}/vetsgpt/chats/{chatId}/attachments/patient`

## Request

- Base URL: `https://vetnio.com/api/v2`
- URL: `https://vetnio.com/api/v2/workspaces/{workspaceId}/vetsgpt/chats/{chatId}/attachments/patient`
- Auth: HTTP bearer

Owner only: detaches the patient from the chat's context for new questions. Attached consultations are not affected, and existing questions retain their captured context on retry. Succeeds when no patient was attached. Returns `404` when the chat does not exist or the caller is not its owner.

## Path parameters

- `workspaceId` string, required: Identifier of the workspace (clinic). The caller must be a member, and VetsGPT must be enabled for them in this workspace.
- `chatId` string, required: Identifier of a VetsGPT chat owned by or explicitly shared with the caller. Unshared chats behave as if they did not exist.

## Response `200`

The patient context was removed.

- object: Acknowledgement returned by VetsGPT mutations that have no resource body.
  - `success` boolean, required: Always `true` on success; failures are returned as errors.

## Other responses

- `400`: Invalid input data
- `401`: Authorization not provided
- `403`: Insufficient access
- `404`: Not found
- `500`: Internal server error

---

[API](https://skmtc.dev/vetnio/apis/vetnio-api.md) - [All operations](https://skmtc.dev/vetnio/apis/vetnio-api/llms.txt) - [OpenAPI document](https://skmtc.dev/vetnio/apis/vetnio-api/revisions/d004afd5617d?raw)