Get client profile by email in VTEX Checkout
A documented VTEX Checkout 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 client profile by email
- GETReads data · Cart attachments
vtex.local/api/checkout/pub/profiles
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 Checkout 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 Checkout operations
- Add cart itemsPOST · changes data
- Add payment dataPOST · changes data
- Process orderPOST · changes data
- Add coupons to the cartPOST · changes data
- Place order from an existing cartPOST · changes data
- Cart simulationPOST · changes data
- Update orderForm configurationPOST · changes data
- Update cart itemsPOST · changes data
Questions
- Can HumDay get client profile by email in VTEX Checkout?
- Yes. This operation is published in VTEX Checkout'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 Checkout 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 Checkout.
- 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 Checkout account.
Where this came from
Read from a published API description for VTEX Checkout at raw.githubusercontent.com/vtex/openapi-schemas/master/VTEX - Checkout API.json. The description above is the provider’s own wording, not ours. Last published 2023-03-03.