Get purchase information in VTEX Profile System
A documented VTEX Profile System 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 purchase information
- GETReads data · Purchase information
vtex.local/api/storage/profile-system/profiles/{profileId}/purchase-info
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 Profile System 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 Profile System operations
- Create client profilePOST · changes data
- Create prospectPOST · changes data
- Create or update profile schemaPUT · changes data
- Create client addressPOST · changes data
- Create purchase informationPOST · changes data
- Delete client profileDELETE · changes data
- Updates client profilePATCH · changes data
- Delete prospectDELETE · changes data
Questions
- Can HumDay get purchase information in VTEX Profile System?
- Yes. This operation is published in VTEX Profile System'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 Profile System 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 Profile System.
- 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 Profile System account.
Where this came from
Read from a published API description for VTEX Profile System at raw.githubusercontent.com/vtex/openapi-schemas/master/VTEX - Profile System.json. The description above is the provider’s own wording, not ours. Last published 2023-03-03.