CRUD: Retrieve an invoice payment in Zuora Reference Billing
A documented Zuora Reference Billing 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
CRUD: Retrieve an invoice payment
- GETReads data · Invoice Payments
rest.zuora.com/v1/object/invoice-payment/{id}
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 Zuora Reference Billing 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 Zuora Reference Billing operations
- CRUD: Create an invoice paymentPOST · changes data
- Create an orderPOST · changes data
- Create a standalone invoicePOST · changes data
- Create a paymentPOST · changes data
- Create an event triggerPOST · changes data
- Upload a file for an invoicePOST · changes data
- Email an invoicePOST · changes data
- Create an order asynchronouslyPOST · changes data
Questions
- Can HumDay crud: retrieve an invoice payment in Zuora Reference Billing?
- Yes. This operation is published in Zuora Reference Billing'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 Zuora Reference Billing account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Zuora Reference Billing.
- 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 Zuora Reference Billing account.
Where this came from
Read from a published API description for Zuora Reference Billing at www.zuora.com/wp-content/themes/zuora/yaml/swagger.yaml?v-7.0. The description above is the provider’s own wording, not ours. Last published 2021-08-23.