Create document with custom ID or update entire document
Creates a new document with a custom ID, or updates an entire document if there is already a document with the informed ID.
ℹ️ You can use this request to create or update 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 Type | Example value |
|---|---|
| Boolean | true |
| Currency | 2.5 |
| Date | 1992-11-17 |
| Date_Time | 2016-09-14T19:21:01.3163733Z |
| Decimal | 2.5 |
| meu@email.com | |
| Integer | 1000000 |
| Long | 1000000000 |
| Percent | 85.42 |
| Time | 23:50 |
| URL | https://www.vtex.com |
| Varchar10 | Lorem ipsu |
| Varchar50 | Lorem ipsum dolor sit amet, consectetur adipiscing |
| Varchar750 | Lorem ipsum dolor sit amet, consectetur adipiscing elit... |
| Varchar100 | Lorem ipsum dolor sit amet, consectetur adipiscing elit... |
| Relationship | 5eb31afb-7ab0-11e6-94b4-0a44686e393f |
| Text | Lorem 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:
| Product | Category | Resource |
|---|---|---|
| Dynamic Storage | Dynamic storage generic resources | Insert or update document (not remove) |
| Dynamic Storage | Dynamic storage generic resources | Full access to all documents |
| Dynamic Storage | Dynamic storage generic resources | Master 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.
Path parameters
Two-letter string that identifies the data entity.
Unique identifier of the document.
Headers
Type of the content being sent.
HTTP Client Negotiation Accept Header. Indicates the types of responses the client can understand.
Request body
Example request
{
"{fieldName}": "{fieldValue}"
}Response
No Content