Skip to API content
TalkLabs API Docs v3
Recipes
PUT Users & notifications

Notifications: Mark All Read

Unless your workflow must support use of read notifications, notifications should be deleted when read.

PUT /api/v3/{appid}/user/users/{userid}/notification/notifications_all/markread

Unless your workflow must support use of read notifications, notifications should be deleted when read.

This marks all notifications for a user as read with one api call.

URL Arguments

  • userid : (required) The ID of the user marking the notification as read. This is used to ensure a user can't mark another user's notification as read.
  • delete : (optional, default: true) The read status (true/false) for the notification. If true, all the notifications for the user are deleted. If false, they are marked read.
Request

Parameters

Values in the path and query string.

appid path
string TalkLabs ID required

The application the user belongs to.

Example: your-app-id
userid path
string customer-defined required

Required. The user marking notifications read used to ensure a user can't mark another user's notifications.

Example: u-8842
delete query
boolean

Optional, default true. If true, all of the user's notifications are deleted. If false, they are marked read not deleted .

Example: true
Response

Status codes

Every JSON response uses the API result envelope.

200 OK: success. ApiResult
400 Bad Request ApiResult
403 Forbidden: request is not authorized with a valid token, or the token does not match this appid. ApiResult
500 Internal Server Error ApiResult
Search all 118 endpoints Try “join room”, “moderate”, or “POST”.
Request environment

Connect your application

These values fill request examples and the API console. They stay in this browser tab and are never sent to TalkLabs until you run a request.

Credentials are stored in sessionStorage, not in cookies or analytics.