Remove blocked delivery windows in VTEX Logistics
A documented VTEX Logistics operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Remove blocked delivery windows
- POSTChanges data · Scheduled Delivery
vtex.local/api/logistics/pvt/configuration/carriers/{carrierId}/removedayofweekblocked
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 Logistics operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other VTEX Logistics operations
- Create shipping policyPOST · changes data
- Create/update dockPOST · changes data
- Create/update polygonPUT · changes data
- Create reservationPOST · changes data
- Create/update warehousePOST · changes data
- Create/update holidayPUT · changes data
- Create/Update Pickup PointPUT · changes data
- Calculate SLAPOST · changes data
Questions
- Can HumDay remove blocked delivery windows in VTEX Logistics?
- Yes. This operation is published in VTEX Logistics's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my VTEX Logistics data?
- Yes — this is a POST operation, so it changes something in VTEX Logistics. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- 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 Logistics account.
Where this came from
Read from a published API description for VTEX Logistics at raw.githubusercontent.com/vtex/openapi-schemas/master/VTEX - Logistics API.json. The description above is the provider’s own wording, not ours. Last published 2023-03-03.