Delete customer profile in VTEX Master Data
A documented VTEX Master Data 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
Delete customer profile
- DELETEChanges data · Customer profiles
vtex.local/api/dataentities/Client/documents/{id}
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 Master Data 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 Master Data operations
- Create new customer profilePOST · changes data
- Create new customer addressPOST · changes data
- Create new documentPOST · changes data
- Create partial documentPATCH · changes data
- Update customer profilePATCH · changes data
- Delete customer addressDELETE · changes data
- Update customer addressPATCH · changes data
- Delete documentDELETE · changes data
Questions
- Can HumDay delete customer profile in VTEX Master Data?
- Yes. This operation is published in VTEX Master Data'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 Master Data data?
- Yes — this is a DELETE operation, so it changes something in VTEX Master Data. 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 Master Data account.
Where this came from
Read from a published API description for VTEX Master Data at raw.githubusercontent.com/vtex/openapi-schemas/master/VTEX - Master Data API - v2.json. The description above is the provider’s own wording, not ours. Last published 2023-03-03.