# Email

The Email API provides read access to email records associated with patients, including draft emails and attachments.

**Base path:** `/{tenantName}/{instanceName}/patients/{patientId}/emails`

***

## Endpoints

### GET Get All Emails

**GET** `/{tenantName}/{instanceName}/patients/{patientId}/emails`

Returns all email records for a patient.

#### Query Parameters

| Parameter | Type    | Default | Description                           |
| --------- | ------- | ------- | ------------------------------------- |
| `page`    | integer | `0`     | Page number                           |
| `size`    | integer | `20`    | Results per page                      |
| `status`  | string  | —       | Filter by `SENT`, `DRAFT`, `RECEIVED` |

#### Example Response `200 OK`

```json
{
  "data": [
    {
      "id": "email-uuid",
      "patientId": "a1b2c3d4",
      "subject": "Care Plan Update",
      "direction": "OUTBOUND",
      "status": "SENT",
      "sentAt": "2026-03-18T11:00:00Z",
      "hasAttachment": true
    }
  ]
}
```

***

### GET Get Email by ID

**GET** `/{tenantName}/{instanceName}/patients/{patientId}/emails/{emailId}`

Returns a single email record with full content and metadata.

***

### GET Download Email Attachment

**GET** `/{tenantName}/{instanceName}/patients/{patientId}/emails/{emailId}/attachment`

Downloads a file attachment from an email record.

***

## Email Drafts

### GET Get All Email Drafts

**GET** `/{tenantName}/{instanceName}/patients/{patientId}/email-drafts`

Returns all saved email drafts for a patient that have not yet been sent.

### GET Get Email Draft by ID

**GET** `/{tenantName}/{instanceName}/patients/{patientId}/email-drafts/{draftId}`


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.welkinhealth.com/developer-and-integration-guide/api-reference/email.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.