<div class="endpoint"><span class="method">GET</span><code>/api/v1/workspaces/&#123;workspaceId&#125;/patients/&#123;patientId&#125;</code></div>

**Operation ID:** `patients.get` · **Access:** PAT with `read` scope and authorized workspace where applicable · **Effect:** `read`.

Read the [patients workflow](/guides/data-model/) before this operation.

## Parameters

| Name | In | Required | Type / allowed values |
| --- | --- | --- | --- |
| `workspaceId` | path | Yes | string |
| `patientId` | path | Yes | string |

## Responses

| HTTP | Content | Schema |
| --- | --- | --- |
| 200 | `application/json` | [Patient](/reference/schemas/patient/) |
| 400 | `application/json` | [ApiError](/reference/schemas/api-error/) |
| 401 | `application/json` | [ApiError](/reference/schemas/api-error/) |
| 403 | `application/json` | [ApiError](/reference/schemas/api-error/) |
| 404 | `application/json` | [ApiError](/reference/schemas/api-error/) |
| 500 | `application/json` | [ApiError](/reference/schemas/api-error/) |

Use `error.code`, `error.issues`, and `requestId` for JSON errors. [Error and recovery guide](/guides/errors-and-retries/).

## cURL

Set the connection variables from the [quickstart](/guides/quickstart/). Set each path variable to an authorized identifier or an allowed parameter value from the table above.

```bash
curl --fail-with-body --request GET \
  "$RIPSCLOUD_BASE_URL/api/v1/workspaces/$WORKSPACE_ID/patients/$PATIENT_ID" \
  --header "Authorization: Bearer $RIPSCLOUD_TOKEN" \
  --header 'Accept: application/json'
```
