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 endpoint and pass the query parameter all=false.

Request Example

Shell

JavaScript

Java

Swift

curl --location --request PUT 'https://api.github.com/repos///notifications' \
--header 'Content-Type: application/json' \
--data-raw '{
    "last_read_at": "2019-01-01T00:00:00.000Z"
}'

Response Example

202 - default

{
    "message": "Unread notifications couldn't be marked in a single request. Notifications are being marked as read in the background."
}

Request

Path Params

owner

string

required

The account owner of the repository. The name is not case sensitive.

repo

string

required

The name of the repository. The name is not case sensitive.

Body Params application/json

last_read_at

string <date-time>

optional

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 format: YYYY-MM-DDTHH:MM:SSZ. Default: The current timestamp.

Examples

Responses

🟢202Response

application/json

Body

message

string

optional

url

string

optional

🟢205Reset Content

Modified at 2023-08-15 02:59:27

List repository notifications for the authenticated user

List stargazers