---
title: "Mark Notification Read"
method: PUT
path: "/fyi/notifications/{notificationId}"
tags: ["tradingFyIsAndNotifications"]
---

# Mark Notification Read

`PUT /fyi/notifications/{notificationId}`

Mark a particular notification message as read or unread.

## Path parameters

- `notificationId` unknown, required

## Response `200`

Successfully enabled or disabled your email notifications.

- NotificationReadAcknowledge
  - `V` integer — Returns 1 to state message was acknowledged.
  - `T` integer — Returns the time in ms to complete the edit.
  - `P` NotificationReadAcknowledgeP — Returns details about the notification read status.
    - `R` integer — Returns if the message was read (1) or unread (0).
    - `ID` string — Returns the ID for the notification.

## Other responses

- `400` — Missing, empty, non-numeric, or out-of-range parameter. The `error` field is always prefixed with `Bad Request:`.
- `401` — Missing, invalid, or unparseable Authorization token.
- `500` — internal server error, returned when incoming request cannot be processed. It can sometimes include subset of bad requests. For example, wrong accountId passed and it can only be detected later in handling request. Error contains reason of the problem.
- `503` — service is unavailable. For example if request takes more than 10s due to some internal service unavailability, request aborted and this status returned

---

[API](https://skmtc.net/interactivebrokers/apis/api-reference.md) · [All operations](https://skmtc.net/interactivebrokers/apis/api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/interactivebrokers/api-reference/revisions/67f9f562c2c6/schema)