Create sub-material library
| Properties | Values |
|---|---|
| HTTP method | POST |
| Interface path | /nd/api/file/create_material_folder |
| Category | File API |
Interface description
Interface path: /nd/api/file/create_material_folder
HTTP method: POST
HTTP method: POST
POST request body parameters
| Parameter | Type | Description (source requirements, defaults and scope) |
|---|---|---|
destDirFileId |
string |
fileId of the destination folder (required) |
name |
string |
The name of the created category library (required) |
accessType |
number |
Optional category visibility; default 0. 0 public, 1 application required, 2 department public, 3 department application required, 4 confidential. |
managerId |
string |
The id of the person in charge (optional) |
departmentIds |
array |
Classification visibility-limited department id of department (optional) Array type [departmentId1,departmentId2] |
assistantIds |
array |
ID of the material library assistant (optional) Array type [usrId1,userId2] |
Scroll horizontally to view all columns
The return information is as follows
{"code":0, "success":true, "materialFolder": {}}Call instructions
- Before calling, you need to complete Get token or the corresponding login-free authentication, and carry
Authorization: Bearer <access_token>in the request header. - If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail.
- Category: File API.