Create or update partial document in VTEX MasterData
A documented VTEX MasterData operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Create or update partial document
- PATCHChanges data · Documents
vtex.local/api/dataentities/{acronym}/documents
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which VTEX MasterData operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other VTEX MasterData operations
- Create new documentPOST · changes data
- Create or update entire documentPUT · changes data
- Delete documentDELETE · changes data
- Update partial documentPATCH · changes data
- Update entire documentPUT · changes data
- Validate Document by ClustersPOST · changes data
- Delete score by fieldDELETE · changes data
- Put score by fieldPUT · changes data
Questions
- Can HumDay create or update partial document in VTEX MasterData?
- Yes. This operation is published in VTEX MasterData's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my VTEX MasterData data?
- Yes — this is a PATCH operation, so it changes something in VTEX MasterData. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your VTEX MasterData account.
Where this came from
Read from a published API description for VTEX MasterData at raw.githubusercontent.com/vtex/openapi-schemas/master/VTEX - MasterData API - v10.2.json. The description above is the provider’s own wording, not ours. Last published 2023-03-03.