ManualChapters
Introduction
ManualChapters organize ManualEntries in a nested structure and define the Entity Permissions inherited by their descendants.
Model Definition
Alias
manualChapter
Relations
entityPermissions
Morph many
entity_permissions.restrictable_type, entity_permissions.restrictable_id
Computed Properties
hash- Hashed representation of the chapterid.
Capabilities
Entity Permissions - Chapters own direct
viewandadministrategrants; descendant chapters and entries are additionally constrained by their ancestors.URL Context - Chapter URLs resolve to access-checked context information.
Translations - The
titlefield is translatable.Notifications - Creating or updating an active chapter can notify eligible users selected through its inherited access chain.
List
List ManualChapters visible to the current authenticated User.
Definition
GET /api/manual/chapters
Behavior
The Restricted Scope combines direct
viewgrants with the access constraints of every parent chapter.
Example Request
Example Response
Show
Show a single ManualChapter by ID, hash, or slug.
Definition
GET /api/manual/chapters/{manualChapter}
Route Parameters
manualChapter
integer | string
ManualChapter ID, hash, or slug.
Behavior
Access is checked recursively against the chapter and every parent chapter.
Example Request
Example Response
Admin: List
List ManualChapters available in the administration scope.
Definition
GET /api/administration/manual/chapters
Behavior
Administration permissions determine whether the result is unrestricted or limited to owned and permitted chapters.
Soft-deleted chapters are included.
Example Request
Example Response
Admin: Show
Show a single ManualChapter in the administration scope.
Definition
GET /api/administration/manual/chapters/{manualChapter}
Route Parameters
manualChapter
integer | string
ManualChapter ID, hash, or slug.
Behavior
The user must have unrestricted chapter administration access, own the chapter, or receive an applicable
administrategrant through its hierarchy.
Example Request
Example Response
Admin: Create
Create a new ManualChapter.
Definition
POST /api/administration/manual/chapters
Request Keys
lang_id
string
system language
Language key for the translatable title.
title*
string
-
Chapter title, unique among siblings with the same parent_id.
slug
string
slugged title
Chapter slug, unique among siblings with the same parent_id.
enumeration
boolean
false
Whether clients should enumerate the chapter.
active
boolean
true
Whether the chapter is active.
sort_number
integer
end of parent
Position among chapters with the same parent_id.
Keys with * are required.
Behavior
The authenticated user becomes the owner; a client-provided
user_idis ignored.The slug is normalized from
slugortitle, and missing, invalid, or out-of-rangesort_numbervalues are normalized within the selected parent.Creating an active chapter can notify eligible users selected by its direct and inherited
viewgrants.
Example Request
Example Response
Admin: Update
Update an existing ManualChapter.
Definition
PUT /api/administration/manual/chapters/{manualChapter}
Route Parameters
manualChapter
integer | string
ManualChapter ID, hash, or slug.
Request Keys
parent_id
integer | null
New parent chapter ID.
lang_id
string
New language key for the translatable title.
title
string
New title, unique among siblings with the resulting parent_id.
slug
string
New slug, unique among siblings with the resulting parent_id.
enumeration
boolean
Whether clients should enumerate the chapter.
active
boolean
Whether the chapter is active.
sort_number
integer
New position among chapters with the resulting parent_id.
Behavior
A client-provided
user_idis ignored. Changing the parent, title, or slug transfers ownership to the authenticated user.When
parent_idis omitted, the current parent is retained for validation. Changing the parent or sort position normalizes both affected sibling orders.The slug is normalized from an explicitly supplied
slugor the updatedtitle.Changing
titleremoves stored translations for the previous title. Activating a chapter or changing its title can trigger notifications.
Example Request
Example Response
Admin: Delete
Delete an existing ManualChapter.
Definition
DELETE /api/administration/manual/chapters/{manualChapter}
Route Parameters
manualChapter
integer | string
ManualChapter ID, hash, or slug.
Behavior
The chapter is soft-deleted, its position is removed from the sibling order, and its notifications are deleted.
Descendant chapters and contained entries are deleted recursively.
Example Request
Example Response
Last updated