Create Single Document

Create a single document.

POST/api/{version}/objects/documents

Headers

Name	Description
`Content-Type`	`multipart/form-data`
`Accept`	`application/json` (default) or `application/xml`

Body Parameters

There are multiple ways to create a document.

Create Document from Uploaded File

Most documents in your Vault are created from uploaded source files, such as a file from your computer. Learn about Supported File Formats in Vault Help. Once uploaded with values assigned to document fields, Vault generates the viewable rendition, e.g., "mydocument.docx.pdf". Learn about Viewable Renditions in Vault Help.

Name	Description
`file`	The filepath of the source document. The maximum allowed file size is 4GB.
`type__v`	The name of the document type to assign to the new document.
`subtype__v`	The name of the document subtype (if one exists on the document type).
`classification__v`	The name of the document classification (if one exists on the document subtype).
`lifecycle__v`	The name of the document lifecycle to assign to the new document.
`major_version_number__v`	The major version number to assign to the new document.
`minor_version_number__v`	The minor version number to assign to the new document.

Create Document from Template

When you create the new document, Vault copies the template file and uses that copy as the source file for the new document. This process bypasses the content upload process and allows for more consistent document creation. Document templates are associated with a specific document type, like documents themselves. Learn about Document Templates in Vault Help.

Name	Description
`fromTemplate`	The name of the template to apply.
`type__v`	The name of the document type to assign to the new document.
`subtype__v`	The name of the document subtype (if applicable).
`classification__v`	The name of the document classification (if one exists on the document subtype).
`lifecycle__v`	The name of the document lifecycle to assign to the new document.
`major_version_number__v`	The major version number to assign to the new document.
`minor_version_number__v`	The minor version number to assign to the new document.

Create Content Placeholder Document

Creating a content placeholder document is just like creating a document from an uploaded file, but the file parameter is not included in the request. Learn about Content Placeholders in Vault Help. Admin may set other standard or custom document fields to required in your Vault.

Name	Description
`name__v`	The name of the new document.
`type__v`	The name of the document type to assign to the new document.
`subtype__v`	The name of the document subtype (if one exists on the document type).
`classification__v`	The name of the document classification (if one exists on the document subtype).
`lifecycle__v`	The name of the document lifecycle to assign to the new document.
`major_version_number__v`	The major version number to assign to the new document.
`minor_version_number__v`	The minor version number to assign to the new document.

Create Unclassified Document

Unclassified documents are documents which have a source file, but no document type. Learn about Unclassified Documents in Vault Help.

Name	Description
`file`	The filepath of the source document. The maximum allowed file size is 4GB.
`type__v`	Set the document type to "Undefined".
`lifecycle__v`	Set the document lifecycle to "Unclassified".

In eTMF Vaults, you can also (optionally) set the following fields:

product__v
study__v
study_country__v
site__v

Any other fields included in the input will be ignored. The document name__v will default to the name of the uploaded file.

Create CrossLink Document

When creating a CrossLink document, you must include all document fields that are required for the specified document type/subtype/classification and no file is uploaded. You must also specify the Vault ID and document ID for the source document which will be bound to the new CrossLink document. Learn about CrossLinks in Vault Help.

Name	Description
`name__v`	The name of the new CrossLink document.
`type__v`	The name of the document type to assign to the new CrossLink document.
`subtype__v`	The name of the document subtype (if one exists on the document type).
`classification__v`	The name of the document classification (if one exists on the document subtype).
`lifecycle__v`	The name of the document lifecycle to assign to the new CrossLink document.
`major_version_number__v`	The major version number to assign to the new CrossLink document
`minor_version_number__v`	The minor version number to assign to the new CrossLink document.
`source_vault_id__v`	The Vault `id` field value of the Vault containing the source document that will be bound to the new CrossLink document. Learn more.
`source_document_id__v`	The document `id` field value of the source document that will be bound to the new CrossLink document.
`source_binding_rule__v`	Optional: Possible values are `Latest version`, `Latest Steady State version`, or `Specific Document version`. These define which version of the source document will be bound to the CrossLink document. If not specified, this defaults to the `Latest Steady State version`.
`bound_source_major_version__v`	Optional: When the `source_binding_rule__v` is set to `Specific Document version`, you must specify the major version number of the source document to bind to the CrossLink document.
`bound_source_minor_version__v`	Optional: When the `source_binding_rule__v` is set to `Specific Document version`, you must specify the minor version number of the source document to bind to the CrossLink document.

Request

curl -X POST -H "Authorization: {SESSION_ID}" \
-H "Content-Type: multipart/form-data" \
-F "file=gludacta-document-01.docx" \
-F "name__v=Gludacta Document" \
-F "type__v=Promotional Piece" \
-F "subtype__v=Advertisement" \
-F "classification__v=Web" \
-F "lifecycle__v=Promotional Piece" \
-F "major_version_number__v=0" \
-F "minor_version_number__v=1" \
-F "product__v=0PR0303" \
-F "external_id__v=GLU-DOC-0773" \
https://myvault.veevavault.com/api/v18.2/objects/documents

Response

{
    "responseStatus": "SUCCESS",
    "responseMessage": "successfully created document",
    "id": 773
}

Response Details

On SUCCESS, the document is created and assigned a system-managed document id field value.