Get hook configuration in VTEX Orders
A documented VTEX Orders 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 hook configuration
- GETReads data · Order hook
vtex.local/api/orders/hook/config
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 Orders 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 Orders operations
- Create or update hook configurationPOST · changes data
- Order invoice notificationPOST · changes data
- Commit feed itemsPOST · changes data
- Update order's partial invoice (send tracking number)PATCH · changes data
- Create or update feed configurationPOST · changes data
- Delete hook configurationDELETE · changes data
- Send payment notificationPOST · changes data
- Delete feed configurationDELETE · changes data
Questions
- Can HumDay get hook configuration in VTEX Orders?
- Yes. This operation is published in VTEX Orders'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 Orders 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 Orders.
- 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 Orders account.
Where this came from
Read from a published API description for VTEX Orders at raw.githubusercontent.com/vtex/openapi-schemas/master/VTEX - Orders API.json. The description above is the provider’s own wording, not ours. Last published 2023-03-03.