/api/helpdesk/forms/folders/{folderId}/members

Exposes HelpDesk form folders as a hierarchical WebAPI resource.

GET /api/helpdesk/forms/folders returns the protected root node with compact summaries of its direct forms and one shallow level of child summaries. Resolve a child folder for its direct contents; descendants are never embedded recursively. Individual folders support normal create, update, and delete operations. New folders default to FolderSharingMode#PRIVATE. A normal delete is deliberately limited to empty folders; recursive deletion is an explicit confirmation-protected tree action. Read-only identifiers are accepted and ignored when a GET representation is sent back unchanged.

Explicit users and groups for RESTRICTED sharing.

# Request
GET /api/helpdesk/forms/folders/<folderId>/members HTTP/1.1
Accept: application/json
Authorization: Bearer <access-token>

# Response
HTTP/1.1 200 OK
Content-Type: application/json

[
    {
        "id": "835qzosebu9m2fejkykc228mu",
        "type": "group"
    }
]

Explicit users and groups for RESTRICTED sharing.

# Request
PUT /api/helpdesk/forms/folders/<folderId>/members HTTP/1.1
Accept: application/json
Authorization: Bearer <access-token>
Content-Type: application/json

[
    {
        "id": "835qzosebu9m2fejkykc228mu",
        "type": "group"
    }
]

# Response
HTTP/1.1 200 OK
Content-Type: application/json

[
    {
        "id": "835qzosebu9m2fejkykc228mu",
        "type": "group"
    }
]

The status codes 400, 403, 404, 405, 406, 409, 413, 415, and 500 use the same ApiError JSON error format:

{
    "status": 404,
    "code": "route_not_found",
    "message": "The requested API route does not exist.",
    "details": []
}

Request and response schemas used on this page.