Automate VTEX MasterData

What HumDay can do in VTEX MasterData

12 documented operations change something in VTEX MasterData.

• POSTCreate new document/api/dataentities/{acronym}/documents
• PATCHCreate or update partial document/api/dataentities/{acronym}/documents
• PUTCreate or update entire document/api/dataentities/{acronym}/documents
• DELETEDelete document/api/dataentities/{acronym}/documents/{id}
• PATCHUpdate partial document/api/dataentities/{acronym}/documents/{id}
• PUTUpdate entire document/api/dataentities/{acronym}/documents/{id}
• POSTValidate Document by Clusters/api/dataentities/{acronym}/documents/{id}/clusters
• PUTPut scores/api/dataentities/{acronym}/documents/{id}/score
• DELETEDelete score by field/api/dataentities/{acronym}/documents/{id}/score/{field-name}
• PUTPut score by field/api/dataentities/{acronym}/documents/{id}/score/{field-name}
• POSTSave attachment/api/dataentities/{acronym}/documents/{id}/{field}/attachments
• PUTPut version/api/dataentities/{acronym}/documents/{id}/versions/{versionId}

What HumDay can read from VTEX MasterData

These are the operations a schedule or a trigger can watch.

• GETList data entities/api/dataentities
• GETSearch documents/api/dataentities/{acronym}/search
• GETGet data entity structure/api/dataentities/{acronym}
• GETGet document/api/dataentities/{acronym}/documents/{id}
• GETScroll documents/api/dataentities/{acronym}/scroll
• GETList versions/api/dataentities/{acronym}/documents/{id}/versions
• GETRetrieve attachment/api/dataentities/{acronym}/documents/{id}/{field}/attachments/{file-name}
• GETGet version/api/dataentities/{acronym}/documents/{id}/versions/{versionId}

How automating VTEX MasterData works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live VTEX MasterData account.
4. Grant access, then go live. You approve the specific VTEX MasterData operations it may use — and only those.

Automate VTEX MasterData with these

• VTEX Catalog162 operations
• VTEX Catalog Seller Portal16 operations
• VTEX Checkout32 operations
• VTEX Customer Credit26 operations
• VTEX Do8 operations
• VTEX GiftCard11 operations
• VTEX GiftCard Hub15 operations
• VTEX Headless CMS3 operations
• VTEX Intelligent Search7 operations
• VTEX Legacy Search15 operations
• VTEX License Manager12 operations
• VTEX Logistics53 operations

Questions about VTEX MasterData automation

Can HumDay connect to VTEX MasterData?

Yes. HumDay reads VTEX MasterData's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 20 operations are documented.

Do I need to write code to automate VTEX MasterData?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your VTEX MasterData account.

What can HumDay do in VTEX MasterData?

12 of the 20 documented operations change something in VTEX MasterData, and 8 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my VTEX MasterData account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to VTEX MasterData is held behind that approval.

Where this came from

The operations above are read from a published API description for VTEX MasterData at raw.githubusercontent.com/vtex/openapi-schemas/master/VTEX - MasterData API - v10.2.json. Descriptions are the provider’s own words, not ours. Last published 2023-03-03.