Mark Notifications Read
Marks the authenticated user's notifications as read: one experience's (experience_id) or everything (all: true) — exactly one of the two. Requires a user credential. Responds with the refreshed badge rows for the affected scope.
Headers
A unique key that makes this request safe to retry. See Idempotent requests.
Request body
Example request
{
"all": true,
"experience_id": "exp_xxxxxxxxxxxxxx"
}Response
notifications marked read
Example response
{
"data": [
{
"account_id": "biz_xxxxxxxxxxxxxx",
"experience_id": "exp_xxxxxxxxxxxxxx",
"last_viewed_at": "2026-01-01T12:00:00.000Z"
}
]
}Changes
Changed in 4 of the 74 revisions of this API.7
- ○
added the non-success response with the status
response-non-success-status-added
- ○
- ○
added the optional property
/to the response with the statusresponse-optional-property-added
- ○
added the optional property
/to the response with the statusresponse-optional-property-added
- ○
added the optional property
/to the response with the statusresponse-optional-property-added
- ○
added the optional property
/to the response with the statusresponse-optional-property-added
This revision also has 9 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○
- ○
the security scope
user:notifications:updatewas added to the endpoint's security schemebearerAuthapi-security-scope-added
This revision also has 16 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○
- ○
endpoint added
endpoint-added
This revision also has 4 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○
Of the 74 revisions, 1 has no diff computed.