Automate Zuora Reference Billing
HumDay reads Zuora Reference Billing’s own published API description and derives 428 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What Zuora Reference Billing is
# Introduction Welcome to the reference for the Zuora Billing REST API! To learn about the common use cases of Zuora Billing REST APIs, check out the [API Guides](https://www.zuora.com/developer/api-guides/). In addition to Zuora API Reference; Billing, we also provide API references for other Zuora products: * [API Reference: Collect](https://www.zuora.com/developer/collect-api/) * [API Reference
API host: rest.zuora.com
What HumDay can do in Zuora Reference Billing
256 documented operations change something in Zuora Reference Billing. The 65 most useful are listed here.
- POSTCRUD: Create an invoice payment
/v1/object/invoice-payment - POSTCreate an order
/v1/orders - POSTCreate a standalone invoice
/v1/invoices - POSTCreate a payment
/v1/payments - POSTCreate an event trigger
/events/event-triggers - POSTUpload a file for an invoice
/v1/invoices/{invoiceId}/files - POSTEmail an invoice
/v1/invoices/{invoiceId}/emails - POSTCreate an order asynchronously
/v1/async/orders - POSTCRUD: Create a contact
/v1/object/contact - POSTCRUD: Create a payment
/v1/object/payment - POSTCreate a revenue schedule for a debit memo item (distribute by date range)
/v1/revenue-schedules/debit-memo-items/{dmi-id} - POSTCreate a revenue schedule for a credit memo item (manual distribution)
/v1/revenue-schedules/credit-memo-items/{cmi-id} - POSTCRUD: Create a taxation item
/v1/object/taxation-item - POSTCreate a revenue schedule for an invoice item (manual distribution)
/v1/revenue-schedules/invoice-items/{invoice-item-id} - POSTCreate a revenue schedule by subscription charge key
/v1/revenue-schedules/subscription-charges/{charge-key} - PUTUpdate an order line item
/v1/order-line-items/{itemId} - POSTCreate a revenue schedule for an invoice item adjustment (manual distribution)
/v1/revenue-schedules/invoice-item-adjustments/{invoice-item-adj-key} - POSTUpload a usage file
/v1/usage - POSTCreate a debit memo from a charge
/v1/debitmemos - POSTCreate a credit memo from a charge
/v1/creditmemos - POSTCreate a payment run
/v1/payment-runs - POSTCreate a subscription
/v1/subscriptions - POSTUpload a file for a custom object bulk job
/objects/jobs/{id}/files - POSTCreate a payment method
/v1/payment-methods - POSTCreate document properties
/v1/document-properties - PUTCRUD: Update an invoice payment
/v1/object/invoice-payment/{id} - POSTUpload a file for a debit memo
/v1/debitmemos/{debitMemoId}/files - POSTCreate an email template
/notifications/email-templates - POSTCreate a debit memo from an invoice
/v1/invoices/{invoiceId}/debitmemos - PUTMulti-entity: Send user access requests
/v1/users/{username}/request-access - POSTUpload a file for a credit memo
/v1/creditmemos/{creditMemoId}/files - POSTCreate a credit memo from an invoice
/v1/invoices/{invoiceId}/creditmemos - POSTCRUD: Create a usage record
/v1/object/usage - POSTCreate a revenue schedule for a debit memo item (distribute by date range)
/v1/revenue-schedules/debit-memo-items/{dmi-id}/distribute-revenue-with-date-range - POSTPreview an order
/v1/orders/preview - POSTCreate a revenue schedule for a credit memo item (distribute by date range)
/v1/revenue-schedules/credit-memo-items/{cmi-id}/distribute-revenue-with-date-range - POSTCreate a notification definition
/notifications/notification-definitions - PUTUpdate custom fields on revenue items by revenue event number
/v1/revenue-items/revenue-events/{event-number} - POSTCreate a revenue schedule for an invoice item (distribute by date range)
/v1/revenue-schedules/invoice-items/{invoice-item-id}/distribute-revenue-with-date-range - POSTCRUD: Create a payment method
/v1/object/payment-method - POSTUpdate order line items
/v1/order-line-items/bulk - POSTCRUD: Create an invoice adjustment
/v1/object/invoice-adjustment - POSTCreate an Apple Pay payment method
/v1/payment-methods/decryption - POSTCreate a credit card payment method
/v1/payment-methods/credit-cards - POSTCRUD: Create a product rate plan charge
/v1/object/product-rate-plan-charge - DELETEDelete a taxation item
/v1/taxationitems/{id} - PUTUpdate a taxation item
/v1/taxationitems/{id} - PUTUpdate an invoice
/v1/invoices/{invoiceId} - DELETEDelete an order
/v1/orders/{orderNumber} - DELETEDelete a payment
/v1/payments/{paymentId} - PUTUpdate a payment
/v1/payments/{paymentId} - POSTCreate a revenue schedule for an invoice item adjustment (distribute by date range)
/v1/revenue-schedules/invoice-item-adjustments/{invoice-item-adj-key}/distribute-revenue-with-date-range - DELETEDelete an event trigger
/events/event-triggers/{id} - PUTUpdate an event trigger
/events/event-triggers/{id} - POSTPreview an order asynchronously
/v1/async/orders/preview - POSTSubmit a data query
/query/jobs - POSTCreate an account
/v1/accounts - POSTMulti-entity: Create an entity
/v1/entities - PUTUpdate invoices
/v1/invoices - POSTCreate an attachment
/v1/attachments - POSTCreate a journal run
/v1/journal-runs - POSTCreate sequence sets
/v1/sequence-sets - DELETECRUD: Delete a contact
/v1/object/contact/{id} - PUTCRUD: Update a contact
/v1/object/contact/{id} - DELETECRUD: Delete an invoice
/v1/object/invoice/{id}
What HumDay can read from Zuora Reference Billing
These are the operations a schedule or a trigger can watch.
- GETList event triggers
/events/event-triggers - GETList all files of an invoice
/v1/invoices/{invoiceId}/files - GETList all items of an invoice
/v1/invoices/{invoiceId}/items - GETList revenue items by revenue event number
/v1/revenue-items/revenue-events/{event-number} - GETRetrieve a revenue schedule by invoice item ID
/v1/revenue-schedules/invoice-items/{invoice-item-id} - GETList email notification histories
/v1/notification-history/email - GETRetrieve an order line item
/v1/order-line-items/{itemId} - GETList orders
/v1/orders - GETList data query jobs
/query/jobs - GETList payments
/v1/payments - GETList payment runs
/v1/payment-runs - GETList workflow tasks
/workflows/tasks - GETList all payment gateways
/v1/paymentgateways - GETCRUD: Retrieve an invoice item
/v1/object/invoice-item/{id} - GETList all parts of a payment
/v1/payments/{paymentId}/parts - GETCRUD: Retrieve an invoice payment
/v1/object/invoice-payment/{id} - GETRetrieve a notification history deletion task
/notifications/history/tasks/{id} - GETCRUD: Retrieve an invoice split item
/v1/object/invoice-split-item/{id} - GETList email templates
/notifications/email-templates - GETList subscription terms
/v1/orders/term/{subscriptionNumber} - GETList order metrics for an evergreen subscription
/v1/orders/{orderNumber}/evergreenMetrics/{subscriptionNumber} - GETList ramp metrics by order number
/v1/orders/{orderNumber}/ramp-metrics - GETCRUD: Retrieve a refund invoice payment
/v1/object/refund-invoice-payment/{id} - GETList orders of an invoice owner
/v1/orders/invoiceOwner/{accountNumber} - GETMulti-entity: List all entities that a user can access
/v1/users/{username}/accessible-entities - GETList all application parts of an invoice
/v1/invoices/{invoiceId}/application-parts - GETList notification definitions
/notifications/notification-definitions - GETList orders by subscription number
/v1/orders/subscription/{subscriptionNumber} - GETList orders of a subscription owner
/v1/orders/subscriptionOwner/{accountNumber} - GETList all payment part items
/v1/payments/{paymentId}/parts/{partid}/itemparts - GETList all revenue items of a revenue schedule
/v1/revenue-items/revenue-schedules/{rs-number} - GETRetrieve a revenue schedule by debit memo item ID
/v1/revenue-schedules/debit-memo-items/{dmi-id} - GETList all revenue events of a revenue schedule
/v1/revenue-events/revenue-schedules/{rs-number} - GETRetrieve a revenue schedule by credit memo item ID
/v1/revenue-schedules/credit-memo-items/{cmi-id} - GETList all taxation items of an invoice item
/v1/invoices/{invoiceId}/items/{itemId}/taxation-items
How automating Zuora Reference Billing works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live Zuora Reference Billing account.
- Grant access, then go live. You approve the specific Zuora Reference Billing operations it may use — and only those.
Popular Zuora Reference Billing integrations
Connect Zuora Reference Billing to the tools people pair it with most.
- Zuora Reference Billing and OData for namespace microsoft.graphintegration
- Zuora Reference Billing and Cloudflareintegration
- Zuora Reference Billing and NetBoxintegration
- Zuora Reference Billing and GitHubintegration
- Zuora Reference Billing and Mistintegration
- Zuora Reference Billing and Loket.nlintegration
- Zuora Reference Billing and Atlassian The Jira Cloud platformintegration
- Zuora Reference Billing and Magento B2Bintegration
- Zuora Reference Billing and Stripeintegration
- Zuora Reference Billing and bunqintegration
- Zuora Reference Billing and DocuSignintegration
- Zuora Reference Billing and Zoomintegration
Automate Zuora Reference Billing with these
- Stripe442 operations
- bunq421 operations
- PayRun.IO389 operations
- Sinao272 operations
- Xero Accounting224 operations
- The Plaid191 operations
- Biapi Budgea Documentation167 operations
- Naviplancentral Advicent.FactFinderService151 operations
- Bigredcloud Big Red Cloud111 operations
- Codat Accounting105 operations
- Portfoliooptimizer Portfolio Optimizer83 operations
- Tradematic Cloud67 operations
Categories
Questions about Zuora Reference Billing automation
- Can HumDay connect to Zuora Reference Billing?
- Yes. HumDay reads Zuora Reference Billing's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 428 operations are documented.
- Do I need to write code to automate Zuora Reference Billing?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Zuora Reference Billing account.
- What can HumDay do in Zuora Reference Billing?
- 256 of the 428 documented operations change something in Zuora Reference Billing, and 172 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Zuora Reference Billing account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Zuora Reference Billing is held behind that approval.
Where this came from
The operations above are read from a published API description for Zuora Reference Billing at www.zuora.com/wp-content/themes/zuora/yaml/swagger.yaml?v-7.0. Descriptions are the provider’s own words, not ours. Last published 2021-08-23.