SPsparkvault
vaults

Create a folder, or find or make the folders a path names

Changed on

With name: a folder of that name under parent_id (the vault root when absent or null), refused when a folder there already holds the name, in any case and in either Unicode form (composed or decomposed). With path: the folders it names under parent_id, each segment the folder holding that name, matched the same way, under the one before it, or a new folder, as an upload placed by folder_path finds or makes them; the answer is the deepest one, and created says whether any was made. A name is stored composed (NFC). A tree of folders is made this way, each folder by its path under a folder named by id: a folder's own name may hold a /, which a path from the vault root would read as two folders. A read-only (Viewer) session can do neither.

post/vaults/{id}/folders

Request

Path parameters

idstring required

The vault.

Request body

namestring

The new folder's name. Not with path.

pathstring

Slash-delimited folder names, first segment first (e.g. Q3/Board), in the syntax and with the validation of an upload's folder_path, its depth counted from the vault root through parent_id. Not with name.

parent_idstring nullable

The folder to create under; the vault root when absent or null.

Response

The folder made, or with path the deepest folder it names, as every folder read answers it.

Changes

  • a9a10e328ba5Revision changes
    • breaking

      the response's property type changed from object to no type for status

    • breaking

      removed the required property / from the response with the status

    • breaking

      removed the required property / from the response with the status

    • breaking

      removed the required property / from the response with the status

    • breaking

      removed the required property / from the response with the status

    • breaking

      removed the required property / from the response with the status

    • warning

      removed the optional property / from the response with the status

    • info

      added subschema #2 to the response property allOf list for the response status

    • info

      the response property / became required for the status

    • info

      the response property / became required for the status

    • info

      the response property / became required for the status

    • info

      the response property / became required for the status

    • info

      the response property became required for the status

    • info

      the response property became required for the status

    • info

      the response property became required for the status

    • info

      the response property became required for the status

    • info

      the response property / became required for the status

    • info

      the response property / became required for the status

    • info

      the response property / became required for the status

    • info

      the response property / became required for the status

    • info

      added the required property / to the response with the status

    • info

      added the required property / to the response with the status

    • info

      added the required property / to the response with the status

    • info

      added the required property / to the response with the status

  • 56d7c265a77aRevision changes
    • breaking

      the response property / became nullable for the status

    • breaking

      the response property / became nullable for the status

    • breaking

      the response property / became nullable for the status

    • breaking

      the response property / became nullable for the status