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

# Notifications

> List the account's unread notifications, and mark one as read by deleting it.

The notifications endpoints work as an unread queue. `GET /notifications/` returns only the **unread** notifications for the authenticated account, and `DELETE /notifications/{notification_id}` **marks one as read**. Deleting a notification is how you mark it read, and once you have, the list stops returning it.

All requests go to `https://api.nodemaven.com/api/v2/base/` and carry the header `Authorization: x-api-key YOUR_API_KEY`. See the [NodeMaven API overview](/proxy-api/overview) for the shared basics.

## Endpoints

| Method | Path | What it does | Responses |
| - | - | - | - |
| `GET` | `/notifications/` | List the account's unread notifications | 200 |
| `DELETE` | `/notifications/{notification_id}` | Mark a notification as read | 204 |

## Listing unread notifications

`GET /notifications/` lists the unread notifications for the account the API key belongs to. Notifications you have already marked read are not included, so the list is always the outstanding ones.

```bash theme={null}
curl https://api.nodemaven.com/api/v2/base/notifications/ \
  -H "Authorization: x-api-key YOUR_API_KEY"
```

## Marking a notification as read

`DELETE /notifications/{notification_id}` marks a single notification as read. The `notification_id` is a uuid in the path and it is required.

```bash theme={null}
curl -X DELETE https://api.nodemaven.com/api/v2/base/notifications/NOTIFICATION_ID \
  -H "Authorization: x-api-key YOUR_API_KEY"
```

A successful call returns 204, so no body comes back. The status code alone confirms the notification is now read.


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