Skip to content

Marks one notification read for the current user and returns the recalculated unread count.

When the notification is tied to a post, every other notification for that same post is marked read at the same time, so opening one item clears the whole thread rather than a single row.

Endpoint

  • Method: POST

  • Path: /notifications/mark-read/{notification_id}

  • Edition: Core

  • Controller: NotificationsController@markAsRead

  • Route source: fluent-community/app/Http/Routes/api.php:133

  • Controller source: fluent-community/app/Http/Controllers/NotificationsController.php

  • Requires a signed-in user; only the caller own subscriber rows are touched.

Live sample

The request and response below were recorded against a running FluentCommunity install and then anonymised — member names, emails, avatars and post content are fictional, and long collections are trimmed to a few entries.

POST Mark Notification Read

POST
/notifications/mark-read/{notification_id}

Marks one notification read for the current user and returns the recalculated unread count.

Controller: NotificationsController@markAsRead
Route source: fluent-community/app/Http/Routes/api.php:133

Authorizations

ApplicationPasswords

WordPress Application Passwords — use Basic auth with username:application_password.

Type
API Key (header: Authorization)

Parameters

Path Parameters

notification_id*

Notification ID extracted from the URL path.

Type
integer
Required

Responses

Successful response

application/json
JSON
{
  
"unread_count": 0
}

Playground

Authorization
Variables
Key
Value

Samples

Powered by VitePress OpenAPI

FluentCommunity developer documentation