v50

latestOpenAPI 3.0.0raw.githubusercontent.com2026-05-142616180.5 KB
Documents

Create new document

Creates a new document with an ID automatically generated by VTEX, corresponding to a given data entity. The request body is a JSON object where the key is the name of the field.

⚠️ Do not use Master Data as a log, cache, or temporary data store. Writing high volumes of disposable data can trigger API throttling and degrade store performance.

ℹ️ You can use this request to create documents in any given data entity. Because of this, you are not restricted to using the fields exemplified below in your requests. But you should be aware of the fields allowed or required for each document you wish to update.

Custom field types

The table below presents the types of custom fields you can use when creating or updating documents in Master Data v1 and example values.

Field TypeExample value
Booleantrue
Currency2.5
Date1992-11-17
Date_Time2016-09-14T19:21:01.3163733Z
Decimal2.5
Emailmeu@email.com
Integer1000000
Long1000000000
Percent85.42
Time23:50
URLhttps://www.vtex.com
Varchar10Lorem ipsu
Varchar50Lorem ipsum dolor sit amet, consectetur adipiscing
Varchar750Lorem ipsum dolor sit amet, consectetur adipiscing elit...
Varchar100Lorem ipsum dolor sit amet, consectetur adipiscing elit...
Relationship5eb31afb-7ab0-11e6-94b4-0a44686e393f
TextLorem ipsum dolor sit amet, consectetur adipiscing elit...

Permissions

Any user or API key must have at least one of the appropriate License Manager resources to be able to successfully run this request. Otherwise they will receive a status code 403 error. These are the applicable resources for this endpoint:

ProductCategoryResource
Dynamic StorageDynamic storage generic resourcesInsert or update document (not remove)
Dynamic StorageDynamic storage generic resourcesFull access to all documents
Dynamic StorageDynamic storage generic resourcesMaster Data administrator

There are no applicable predefined roles for this resource list. You must create a custom role and add at least one of the resources above in order to use this endpoint.To learn more about machine authentication at VTEX, see Authentication overview.

❗ To prevent integrations from having excessive permissions, consider the best practices for managing API keys when assigning License Manager roles to integrations.

post/api/dataentities/{acronym}/documents

Path parameters

acronymstring required
Example:SP

Two-letter string that identifies the data entity.

Headers

Content-Typestring required

Type of the content being sent.

Acceptstring required

HTTP Client Negotiation Accept Header. Indicates the types of responses the client can understand.

Request body

{fieldName}string

Field name.

Example request

{
  "{fieldName}": "{fieldValue}"
}

Response

Created

idstring

ID of the document that was created, with data entity prefix.

hrefstring

Document reference URL.

documentIdstring

Unique identifier of the document.