# Get attachments

### Description

This service retrieves a specific file attachment associated with a case. It is typically used to download the file or display it within an interface.

***

### Request

#### Restrictions

* Authentication: Requires a successful operator login.
* Authorization: The operator or touchpoint must have the necessary permissions to access the case file.

#### Endpoint

```
GET https://<server-url>/api/v4/cases/files/{attachment_id}
```

#### Path Parameters

| **Parameter**   | **Type** | **Description**                                   |
| --------------- | -------- | ------------------------------------------------- |
| `attachment_id` | Integer  | The unique ID of the file attachment to retrieve. |

#### Parameters

| **Parameter** | **Location**   | **Description**                                                                    |
| ------------- | -------------- | ---------------------------------------------------------------------------------- |
| `touchpoint`  | Query / Header | The identifier for the touchpoint. Use `Thalamus-Touchpoint` for the header.       |
| `token`       | Query / Header | The authentication token for the API session. Use `Thalamus-Token` for the header. |

#### Full URL Example

```
https://<server-url>/api/v4/cases/files/1?touchpoint=test&token=...
```

***

### Response

#### ✅ Successful Response: `200 OK`

Returns the binary file content. The `Content-Type` header of the response will match the MIME type of the stored file (e.g., `application/pdf`, `image/png`).

#### ❌ Unsuccessful Response: `200 OK` (Logical Failure)

If the file cannot be retrieved or the `attachment_id` is invalid, the API returns a success status but with a failure message in the body.

Text

```
FAILED
```