Automate VTEX Suggestions

What VTEX Suggestions is

The **Marketplace API** enables marketplaces and sellers hosted on VTEX to perform their collaborative operations. >⚠️ The marketplace must [create an appKey and appToken](https://developers.vtex.com/docs/guides/getting-started-authentication) for each non-VTEX seller that will use this API. ## Index ### Notification Endpoints used by sellers to notify marketplaces that the price or inventory lang

API host: vtex.local

What HumDay can do in VTEX Suggestions

8 documented operations change something in VTEX Suggestions.

• PUTSave Account's Approval Settings/suggestions/configuration
• PUTSend SKU Suggestion/suggestions/{sellerId}/{sellerSkuId}
• PUTActivate autoApprove in Marketplace's Account/suggestions/configuration/autoapproval/toggle
• DELETEDelete SKU Suggestion/suggestions/{sellerId}/{sellerSkuId}
• PUTMatch Multiple Received SKUs/suggestions/matches/action/{actionName}
• PUTSave Seller's Approval Settings/suggestions/configuration/seller/{sellerId}
• PUTActivate autoApprove Setting for a Seller/suggestions/configuration/autoapproval/toggle/seller/{sellerId}
• PUTMatch Received SKUs individually/suggestions/{sellerId}/{sellerskuid}/versions/{version}/matches/{matchid}

What HumDay can read from VTEX Suggestions

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

• GETGet all SKU suggestions/suggestions
• GETGet Account's Approval Settings/suggestions/configuration
• GETGet autoApprove Status in Account Settings/suggestions/configuration/autoapproval/toggle
• GETGet SKU Suggestion by ID/suggestions/{sellerId}/{sellerSkuId}
• GETGet Seller's Approval Settings/suggestions/configuration/seller/{sellerId}
• GETGet all Versions/suggestions/{sellerId}/{sellerskuid}/versions
• GETGet Version by ID/suggestions/{sellerId}/{sellerskuid}/versions/{version}

How automating VTEX Suggestions 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 Suggestions account.
4. Grant access, then go live. You approve the specific VTEX Suggestions operations it may use — and only those.

Automate VTEX Suggestions 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 Suggestions automation

Can HumDay connect to VTEX Suggestions?

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

Do I need to write code to automate VTEX Suggestions?

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 Suggestions account.

What can HumDay do in VTEX Suggestions?

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

Is my VTEX Suggestions 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 Suggestions is held behind that approval.

Where this came from

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