> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cocoondata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# <access-service>/api/v1/users/me/notifications/email

## URL structure&#x20;

```text theme={null}
https://access-service.xy-company.com/api/v1/users/me/notifications/email
```

## Supported methods and overview&#x20;

* `GET` - used to retrieve information about the currently authenticated [Covata user's](/3.1/admin/administering-users.md)<sup>\*</sup> notification preferences.
* `PUT` - used to modify the currently authenticated Covata user's notification preferences.

> [!NOTE]
>
> The `GET` method takes no parameters.

## Detailed description&#x20;

This API endpoint serves a number of purposes:

* Retrieves information about the currently authenticated Covata user's<sup>\*</sup> notification preferences (as a list that provides details about all other available notification preference options).
* Modifies the currently authenticated Covata user's notification preferences. \

  **Note:** These settings can also be modified through the [My Account](/3.1/user/managing-your-account.md#modifying-your-email-notification-preferences) feature of the [Safe Share web application](/3.1/user.md).

## Supported roles&#x20;

This API endpoint supports the following Covata user [roles](/3.1/admin/administering-users.md#a-users-roles) (as described in the [Covata Platform Administrator's Guide](/3.1/admin.md)):

* [Originator](/3.1/admin/administering-users.md#originator-role)
* [Collaborator](/3.1/admin/administering-users.md#collaborator-role)

The Covata Platform's resources available to one of these Covata users (above) is determined by the access token passed in the [header](/3.1/api/access-service-api-v1-users-me-notifications-email.md#access-service-api-v1-users-me-notifications-email-required-headers) of requests to this endpoint.

## Required headers&#x20;

The appropriate access token as the `Bearer` token:

* `Authorization: Bearer a1b2c3d4-e5f6-g7h8-i9j0-k1l2m3n4o5p6`

The following header is required if the body of the request has a JSON object:

* `Content-Type: application/json`

## Optional parameters&#x20;

The following optional parameters can also be sent in the body of the PUT request, each as individual members of a JSON object:

* **code** - item, daily, weekly or none.

  **Example ():**

## Returns&#x20;

A JSON-formatted response containing the following members:

* **notificationPreferences** - .

  * **name** - .
  * **code** - .
  * **selected** - .

  **Example (response from ...):**

<sup>\*</sup> The currently authenticated user is determined by the access token passed in the [header](/3.1/api/access-service-api-v1-users-me-notifications-email.md#access-service-api-v1-users-me-notifications-email-required-headers) of requests to this endpoint.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.