Get all price tables and their rules in VTEX Pricing
A documented VTEX Pricing 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 all price tables and their rules
- GETReads data · Price Tables
vtex.local/pricing/pipeline/catalog
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 Pricing 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 Pricing operations
- Create or Update Base Price or Fixed PricesPUT · changes data
- Delete PriceDELETE · changes data
- Create or Update Fixed Prices on a price table or trade policyPOST · changes data
- Update rules for a price tablePUT · changes data
- Delete Fixed Prices on a price table or trade policyDELETE · changes data
- List price tablesGET · reads data
- Get Pricing ConfigurationGET · reads data
- Get Fixed PricesGET · reads data
Questions
- Can HumDay get all price tables and their rules in VTEX Pricing?
- Yes. This operation is published in VTEX Pricing'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 Pricing 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 Pricing.
- 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 Pricing account.
Where this came from
Read from a published API description for VTEX Pricing at raw.githubusercontent.com/vtex/openapi-schemas/master/VTEX - Pricing API.json. The description above is the provider’s own wording, not ours. Last published 2023-03-03.