---
title: "Mark repository notifications as read"
method: PUT
path: "/repos/{owner}/{repo}/notifications"
tags: ["activity"]
---

# Mark repository notifications as read

`PUT /repos/{owner}/{repo}/notifications`

Marks all notifications in a repository as "read" for the current user. If the number of notifications is too large to complete in one request, you will receive a `202 Accepted` status and GitHub will run an asynchronous process to mark notifications as "read." To check whether any "unread" notifications remain, you can use the [List repository notifications for the authenticated user](https://docs.github.com/rest/activity/notifications#list-repository-notifications-for-the-authenticated-user) endpoint and pass the query parameter `all=false`.

## Path parameters

- `owner` string, required
- `repo` string, required

## Request body

- object
  - `last_read_at` string, date-time — Describes the last point that notifications were checked. Anything updated since this time will not be marked as read. If you omit this parameter, all notifications are marked as read. This is a timestamp in [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format: `YYYY-MM-DDTHH:MM:SSZ`. Default: The current timestamp.

## Response `202`

Response

- object
  - `message` string
  - `url` string

## Other responses

- `205` — Reset Content

---

[API](https://skmtc.net/github/apis/github-v3-rest-api.md) · [All operations](https://skmtc.net/github/apis/github-v3-rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/github/github-v3-rest-api/versions/a367f7028301/schema)
