Get Version by ID in VTEX Suggestions

What this operation does

Get Version by ID

• GETReads data · Get Versionsvtex.local/suggestions/{sellerId}/{sellerskuid}/versions/{version}

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which VTEX Suggestions operations the program may use, and this is one of them.
3. You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.

Other VTEX Suggestions operations

• Save Account's Approval SettingsPUT · changes data
• Send SKU SuggestionPUT · changes data
• Activate autoApprove in Marketplace's AccountPUT · changes data
• Delete SKU SuggestionDELETE · changes data
• Match Multiple Received SKUsPUT · changes data
• Save Seller's Approval SettingsPUT · changes data
• Activate autoApprove Setting for a SellerPUT · changes data
• Match Received SKUs individuallyPUT · changes data

All 15 VTEX Suggestions operations

Questions

Can HumDay get version by id in VTEX Suggestions?

Yes. This operation is published in VTEX Suggestions's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Does this change anything in my VTEX Suggestions account?

No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in VTEX Suggestions.

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

Where this came from

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