Get Sales Channel Mapping Data in VTEX Marketplace
A documented VTEX Marketplace operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Get Sales Channel Mapping Data
- GETReads data · Sales Channel Mapping
vtex.local/seller-register/pvt/sellers/{sellerId}/sales-channel/mapping
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 Marketplace operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other VTEX Marketplace operations
- Invite Seller LeadPOST · changes data
- Create Seller From LeadPUT · changes data
- Delete Seller LeadDELETE · changes data
- Accept Seller LeadPUT · changes data
- Resend Seller Lead InvitePUT · changes data
- Notify marketplace of price updatePOST · changes data
- Notify marketplace of inventory updatePOST · changes data
- Configure Seller AccountPOST · changes data
Questions
- Can HumDay get sales channel mapping data in VTEX Marketplace?
- Yes. This operation is published in VTEX Marketplace'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 Marketplace 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 Marketplace.
- 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 Marketplace account.
Where this came from
Read from a published API description for VTEX Marketplace at raw.githubusercontent.com/vtex/openapi-schemas/master/VTEX - Marketplace APIs.json. The description above is the provider’s own wording, not ours. Last published 2023-03-03.