Retrieve Invoice by Id in VTEX Customer Credit
A documented VTEX Customer Credit 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
Retrieve Invoice by Id
- GETReads data · Invoices
vtex.local/api/creditcontrol/accounts/{creditAccountId}/invoices/{invoiceId}
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 Customer Credit 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 Customer Credit operations
- Create or change store configurationPUT · changes data
- Mark an invoice as PaidPOST · changes data
- Update email and description of a accountPUT · changes data
- Open an AccountPOST · changes data
- Cancel InvoiceDELETE · changes data
- Change InvoicePUT · changes data
- Add an account HolderPOST · changes data
- Create a Pre AuthorizationPOST · changes data
Questions
- Can HumDay retrieve invoice by id in VTEX Customer Credit?
- Yes. This operation is published in VTEX Customer Credit'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 Customer Credit 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 Customer Credit.
- 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 Customer Credit account.
Where this came from
Read from a published API description for VTEX Customer Credit at raw.githubusercontent.com/vtex/openapi-schemas/master/VTEX - Customer Credit API.json. The description above is the provider’s own wording, not ours. Last published 2023-03-03.