List paged Pickup Points in VTEX Logistics
A documented VTEX Logistics 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
List paged Pickup Points
- GETReads data · Pickup points
vtex.local/api/logistics/pvt/configuration/pickuppoints/_search
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. Read-only access is still yours to grant, and still limited to what the contract needs.
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 list paged pickup points 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.
- Does this change anything in my VTEX Logistics 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 Logistics.
- 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.