For the complete documentation index, see llms.txt. This page is also available as Markdown.

ManualEntryReadUsers

Introduction

ManualEntryReadUsers record explicit reading confirmations for a ManualEntry. Creating a read record also ensures that the same User has a corresponding ManualEntrySeenUser.

List by ManualEntry

List ManualEntryReadUsers visible for a ManualEntry.

Definition

GET /api/manual/entries/{manualEntry}/read-users

Route Parameters

Parameter
Type
Description

manualEntry

integer | string

ManualEntry ID, hash, or slug.

Behavior

  • The user must be able to show the parent entry.

  • intratool accounts are excluded. Without the permission to see all entry read users, the result is limited to users in allowed departments.

Example Request

$client = new GuzzleHttp\Client(['base_uri' => 'https://{tenant}.intratool.de']);
$response = $client->request('GET', '/api/manual/entries/1/read-users', [
    'headers' => ['Authorization' => "Bearer {accessToken}"]
]);

Example Response

Mark as Read

Mark a ManualEntry as read by the current authenticated User.

Definition

POST /api/manual/entries/{manualEntry}/read-users

Route Parameters

Parameter
Type
Description

manualEntry

integer | string

ManualEntry ID, hash, or slug.

Behavior

  • user_id comes from authentication and manual_entry_id comes from the route; request-body values are ignored.

  • Group accounts cannot create read records.

  • The endpoint first creates the corresponding seen record when it does not exist. Repeated requests return the existing read record instead of creating duplicates.

  • Creating the record marks notifications for the entry as read, which also marks those notifications as seen.

Example Request

Example Response

Last updated