Can HumDay connect to VTEX Logistics?

Yes. HumDay reads VTEX Logistics's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 53 operations are documented.

Do I need to write code to automate VTEX Logistics?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your VTEX Logistics account.

What can HumDay do in VTEX Logistics?

28 of the 53 documented operations change something in VTEX Logistics, and 25 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my VTEX Logistics account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to VTEX Logistics is held behind that approval.

Automate VTEX Logistics

HumDay reads VTEX Logistics’s own published API description and derives 53 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What VTEX Logistics is

>Check the [Fulfillment onboarding guide](https://developers.vtex.com/docs/guides/fulfillment). We created this guide to improve the onboarding experience for developers at VTEX. It assembles all documentation on our Developer Portal about fulfillment and is organized by focusing on the developer's journey. Logistics or fulfillment is the module responsible for shipping calculation and inventory m

API host: vtex.local

What HumDay can do in VTEX Logistics

28 documented operations change something in VTEX Logistics.

POSTCreate shipping policy/api/logistics/pvt/shipping-policies
POSTCreate/update dock/api/logistics/pvt/configuration/docks
PUTCreate/update polygon/api/logistics/pvt/configuration/geoshape
POSTCreate reservation/api/logistics/pvt/inventory/reservations
POSTCreate/update warehouse/api/logistics/pvt/configuration/warehouses
PUTCreate/update holiday/api/logistics/pvt/configuration/holidays/{holidayId}
PUTCreate/Update Pickup Point/api/logistics/pvt/configuration/pickuppoints/{pickupPointId}
POSTCalculate SLA/api/logistics/pvt/shipping/calculate
DELETEDelete shipping policies by ID/api/logistics/pvt/shipping-policies/{id}
PUTUpdate shipping policy/api/logistics/pvt/shipping-policies/{id}
POSTAdd blocked delivery windows/api/logistics/pvt/configuration/carriers/{carrierId}/adddayofweekblocked
DELETEDelete dock/api/logistics/pvt/configuration/docks/{dockId}
POSTCreate/update freight values/api/logistics/pvt/configuration/freights/{carrierId}/values/update
DELETEDelete holiday/api/logistics/pvt/configuration/holidays/{holidayId}
DELETEDelete polygon/api/logistics/pvt/configuration/geoshape/{polygonName}
DELETERemove warehouse/api/logistics/pvt/configuration/warehouses/{warehouseId}
DELETEDelete Pickup Point/api/logistics/pvt/configuration/pickuppoints/{pickupPointId}
POSTActivate dock/api/logistics/pvt/configuration/docks/{dockId}/activation
POSTDeactivate dock/api/logistics/pvt/configuration/docks/{dockId}/deactivation
POSTCancel reservation/api/logistics/pvt/inventory/reservations/{reservationId}/cancel
POSTConfirm reservation/api/logistics/pvt/inventory/reservations/{reservationId}/confirm
POSTActivate warehouse/api/logistics/pvt/configuration/warehouses/{warehouseId}/activation
POSTAcknowledgment reservation/api/logistics/pvt/inventory/reservations/{reservationId}/acknowledge
POSTDeactivate warehouse/api/logistics/pvt/configuration/warehouses/{warehouseId}/deactivation
POSTRemove blocked delivery windows/api/logistics/pvt/configuration/carriers/{carrierId}/removedayofweekblocked
PUTUpdate inventory by SKU and warehouse/api/logistics/pvt/inventory/skus/{skuId}/warehouses/{warehouseId}
PUTSave supply lot/api/logistics/pvt/inventory/items/{skuId}/warehouses/{warehouseId}/supplyLots/{supplyLotId}
POSTTransfer supply lot/api/logistics/pvt/inventory/items/{skuId}/warehouses/{warehouseId}/supplyLots/{supplyLotId}/transfer

What HumDay can read from VTEX Logistics

These are the operations a schedule or a trigger can watch.

GETList shipping policies/api/logistics/pvt/shipping-policies
GETList all docks/api/logistics/pvt/configuration/docks
GETList paged polygons/api/logistics/pvt/configuration/geoshape
GETList all holidays/api/logistics/pvt/configuration/holidays
GETList all warehouses/api/logistics/pvt/configuration/warehouses
GETList all pickup points/api/logistics/pvt/configuration/pickuppoints
GETList paged Pickup Points/api/logistics/pvt/configuration/pickuppoints/_search
GETList inventory by SKU/api/logistics/pvt/inventory/skus/{skuId}
GETList dock by ID/api/logistics/pvt/configuration/docks/{dockId}
GETList inventory per dock/api/logistics/pvt/inventory/items/{skuId}/docks/{dockId}
GETList holiday by ID/api/logistics/pvt/configuration/holidays/{holidayId}
GETList polygon by ID/api/logistics/pvt/configuration/geoshape/{polygonName}
GETList warehouse by ID/api/logistics/pvt/configuration/warehouses/{warehouseId}
GETList reservation by ID/api/logistics/pvt/inventory/reservations/{reservationId}
GETList Pickup Point By ID/api/logistics/pvt/configuration/pickuppoints/{pickupPointId}
GETList inventory per warehouse/api/logistics/pvt/inventory/items/{skuId}/warehouses/{warehouseId}
GETRetrieve shipping policy by ID/api/logistics/pvt/shipping-policies/{id}
GETSearch capacity reservations in time range/api/logistics-capacity/resources/carrier@{capacityType}@{shippingPolicyId}/time-frames
GETList supply lots/api/logistics/pvt/inventory/items/{skuId}/warehouses/{warehouseId}/supplyLots
GETList inventory with dispatched reservations/api/logistics/pvt/inventory/items/{itemId}/warehouses/{warehouseId}/dispatched
GETList reservation by warehouse and SKU/api/logistics/pvt/inventory/reservations/{warehouseId}/{skuId}
GETList freight values/api/logistics/pvt/configuration/freights/{carrierId}/{cep}/values
GETList inventory per dock and warehouse/api/logistics/pvt/inventory/items/{skuId}/docks/{dockId}/warehouses/{warehouseId}
GETRetrieve blocked delivery windows/api/logistics/pvt/configuration/carriers/{carrierId}/getdayofweekblocked
GETGet capacity reservation usage by window/api/logistics-capacity/resources/carrier@{capacityType}@{shippingPolicyId}/time-frames/{windowDay}F{windowStartTime}T{windowEndTime}

How automating VTEX Logistics works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live VTEX Logistics account.
Grant access, then go live. You approve the specific VTEX Logistics operations it may use — and only those.

Automate VTEX Logistics with these

Questions about VTEX Logistics automation

Can HumDay connect to VTEX Logistics?: Yes. HumDay reads VTEX Logistics's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 53 operations are documented.
Do I need to write code to automate VTEX Logistics?: No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your VTEX Logistics account.
What can HumDay do in VTEX Logistics?: 28 of the 53 documented operations change something in VTEX Logistics, and 25 read from it. HumDay only ever uses the specific operations your approved contract needs.
Is my VTEX Logistics account safe?: Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to VTEX Logistics is held behind that approval.

Where this came from

The operations above are read from a published API description for VTEX Logistics at raw.githubusercontent.com/vtex/openapi-schemas/master/VTEX - Logistics API.json. Descriptions are the provider’s own words, not ours. Last published 2023-03-03.