ManualEntries
Introduction
ManualEntries contain the Manual content organized by ManualChapters. An entry can belong directly to a chapter or to another entry, and its visibility is constrained by every parent in that hierarchy.
Entries can be published immediately or scheduled, support translations and reactions, and expose seen and read tracking.
The text field uses the shared Rich Text HTML format.
Model Definition
Alias
manualEntry
Relations
entityPermissions
Morph many
entity_permissions.restrictable_type, entity_permissions.restrictable_id
Computed Properties
hash- Hashed representation of the entryid.
Capabilities
Targetables - Eligible users and departments are derived from the intersecting
viewgrants of the entry, its parent entries, and its root chapter.Entity Permissions - Entries own direct
viewandadministrategrants and inherit additional constraints from parent entries and their chapter.URL Context - Entry URLs resolve to access-checked context information.
Translations - The
titleandtextfields are translatable.Notifications - Publishing and relevant content or confirmation changes can notify eligible users.
Reactions - Entries accept reactions when
reactions_forbiddenisfalse.Seen and Read Tracking - Seen records track views, read records capture explicit confirmations, and
reading_confirmationtells clients whether confirmation is required.
List
List ManualEntries visible to the current authenticated User.
Definition
GET /api/manual/entries
Behavior
The Restricted Scope applies the entry's direct Entity Permissions together with every parent entry and chapter constraint.
Scheduled entries are visible to their owner and to users with applicable administration access; other users see them only after publication.
Example Request
Example Response
Show
Show a single ManualEntry by ID, hash, or slug.
Definition
GET /api/manual/entries/{manualEntry}
Route Parameters
manualEntry
integer | string
ManualEntry ID, hash, or slug.
Behavior
Access is checked recursively against the entry, its parent entries, and its chapter.
A scheduled entry is visible before publication only to its owner or a user with applicable administration access.
Example Request
Example Response
Admin: List
List ManualEntries available in the administration scope.
Definition
GET /api/administration/manual/entries
Behavior
Administration permissions determine whether the result is unrestricted or limited to owned and permitted entries.
Soft-deleted and scheduled entries are included when they satisfy the administration scope.
Example Request
Example Response
Admin: Show
Show a single ManualEntry in the administration scope.
Definition
GET /api/administration/manual/entries/{manualEntry}
Route Parameters
manualEntry
integer | string
ManualEntry ID, hash, or slug.
Behavior
The user must have unrestricted entry administration access, own the entry, or receive an applicable
administrategrant through its entry and chapter hierarchy.Scheduled entries remain available in this scope.
Example Request
Example Response
Admin: Create
Create a new ManualEntry.
Definition
POST /api/administration/manual/entries
Request Keys
parent_id
integer | null
null
ID of the parent ManualEntry. Required when manual_chapter_id is omitted.
manual_chapter_id
integer | null
null
ID of the containing ManualChapter. Required when parent_id is omitted.
lang_id
string
system language
Language key for the translatable content.
title*
string
-
Entry title, unique across the selected chapter hierarchy.
slug
string
slugged title
Entry slug, unique across the selected chapter hierarchy.
text*
string
-
Entry content, which can contain HTML.
reading_confirmation
boolean
false
Whether users must explicitly confirm reading.
planned_publish_at
datetime | null
null
Future publication date. Relative dates are accepted.
sort_number
integer
end of parent
Position among entries with the same manual_chapter_id and parent_id.
Keys with * are required.
Behavior
The authenticated user becomes the owner; a client-provided
user_idis ignored.At least one of
parent_idandmanual_chapter_idis required. When both are supplied,parent_idtakes precedence andmanual_chapter_idbecomesnull.The slug is normalized from
slugortitle, and missing, invalid, or out-of-rangesort_numbervalues are normalized within the selected parent.A future
planned_publish_atstorespublished_atasnull. A missing, current, or past value publishes immediately and storesplanned_publish_atasnull; clients cannot setpublished_atindependently.Creating an immediately published entry can notify eligible users. The notification requests confirmation when
reading_confirmationistrue.
Example Request
Example Response
Admin: Reset Relations
Reset selected tracking and reaction relations of an existing ManualEntry.
Definition
POST /api/administration/manual/entries/{manualEntry}/reset
Route Parameters
manualEntry
integer | string
ManualEntry ID, hash, or slug.
Request Keys
Behavior
Only the three resettable relation keys are retained from the request.
At least one relation must be set to
true; an empty request or all-falserequest returns an error.Resetting relations is idempotent with respect to already absent records.
Example Request
Example Response
Admin: Update
Update an existing ManualEntry.
Definition
PUT /api/administration/manual/entries/{manualEntry}
Route Parameters
manualEntry
integer | string
ManualEntry ID, hash, or slug.
Request Keys
lang_id
string
New language key for the translatable content.
title
string
New title, unique across the resulting chapter hierarchy.
slug
string
New slug, unique across the resulting chapter hierarchy.
text
string
New content, which can contain HTML.
reading_confirmation
boolean
Whether users must explicitly confirm reading.
planned_publish_at
datetime | null
New future publication date, or null to publish immediately. Relative dates are accepted.
sort_number
integer
New position among entries with the resulting parent.
Behavior
A client-provided
user_idis ignored. Changing the parent, chapter, title, slug, or text transfers ownership to the authenticated user.When neither parent key is supplied, the current hierarchy is retained. When both are supplied,
parent_idtakes precedence; supplying one sets the other tonull.Changing the parent or sort position normalizes both affected sibling orders. The slug is normalized from an explicitly supplied
slugor the updatedtitle.A changed future
planned_publish_atschedules the entry and clearspublished_at. Setting it tonull, the current time, or a past time publishes immediately. An already published entry cannot be assigned an earlierpublished_atvalue.Changing
titleortextremoves stored translations for the previous content. Publishing or changing content or reading-confirmation state can trigger notifications.
Example Request
Example Response
Admin: Delete
Delete an existing ManualEntry.
Definition
DELETE /api/administration/manual/entries/{manualEntry}
Route Parameters
manualEntry
integer | string
ManualEntry ID, hash, or slug.
Behavior
The entry is soft-deleted, its position is removed from the sibling order, and its notifications are deleted.
Descendant entries are deleted recursively.
Example Request
Example Response
Last updated