Get details of a seller's SKU in VTEX SKU Bindings
A documented VTEX SKU Bindings 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 details of a seller's SKU
- GETReads data · SKU Bindings
vtex.local/sku-binding/pvt/skuseller/{sellerId}/{sellerSkuId}
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 SKU Bindings 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 SKU Bindings operations
- Change Notification with SKU IDPOST · changes data
- Insert SKU BindingPOST · changes data
- Change Notification with Seller ID and Seller SKU IDPOST · changes data
- Bind a seller's SKU to another SKUPUT · changes data
- Remove a seller's SKU BindingPOST · changes data
- Activate SKU BindingPOST · changes data
- Deactivate SKU BindingPOST · changes data
- Get SKU Bindings by SKU IDGET · reads data
Questions
- Can HumDay get details of a seller's sku in VTEX SKU Bindings?
- Yes. This operation is published in VTEX SKU Bindings'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 SKU Bindings 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 SKU Bindings.
- 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 SKU Bindings account.
Where this came from
Read from a published API description for VTEX SKU Bindings at raw.githubusercontent.com/vtex/openapi-schemas/master/VTEX - SKU Bindings API.json. The description above is the provider’s own wording, not ours. Last published 2023-03-03.