v50

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

Create new document

Creates a new document with an ID automatically generated by VTEX, corresponding to a new or existing data entity. If an unexisting dataEntityName is informed in the path, this endpoint will create the data entity as well as the new document. For example, you can create a new customer profile or address.

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

To create a document with a custom ID, refer to the Create document with custom ID endpoint.

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/{dataEntityName}/documents

Path parameters

dataEntityNamestring required
Example:Newsletter

Name of the data entity.

Query parameters

_schemastring
Example:schema

Name of the schema that the document complies with. This field is required when using _where or _fields query parameters.

Headers

Content-Typestring required
Example:application/json

Type of the content being sent.

Acceptstring required
Example:application/json

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

Request body

DocumentRequest required

This can be any pure JSON document. Add new Key-Value pairs to test.

Response

Created

Idstring required

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

Hrefstring required

Document reference URL.

DocumentIdstring required

ID of the document that was created.

All 20 operations