Reference · built on requestConnectorPayments, billing & fraud

Zuora

Accounts, subscriptions, invoices, payments, and usage from Zuora Billing, with callouts on standard and custom events.

Request accessPricing ↗

About

Zuora is a billing and revenue platform. Its object model centers on Account, Order, Subscription, Invoice, and Payment, with bill runs and payment runs that generate invoices and capture payments at scale, plus credit memos, debit memos, refunds, and usage. REST API v1 sits alongside Object Query, Data Query, Workflow, and Custom Objects APIs. Notifications fire callouts to a URL you define when standard or custom events occur.

An operator reads those objects and callouts and proposes a billing correction for your approval, leaving a receipt of what changed and why.

This is a reference listing. It documents what Fibric would read from Zuora and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Accounts, subscriptions, and orders through REST API v1 and Object Query
  • Invoices and invoice items generated by bill runs
  • Payments, refunds, credit memos, and debit memos as payment runs and adjustments post them
  • Usage records tied to rate plan charges
  • Callouts from notification definitions on standard events, custom events, or custom scheduled events
  • Notification histories for callouts and emails

Proposed actions

  • Target capability: propose an order that creates or amends a subscription, since orders are how subscriptions change
  • Target capability: propose a notification definition or callout template change through the Notifications API
  • Target capability: propose resending a failed callout from notification history

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Close the month on time

    Bill run and payment run results are read against the calendar. Invoices still unposted near cutoff are listed for a person to decide on.

    With Month-End Cutoff

  • Match cash to invoices

    Payments and their applied invoices are read from the account. Unapplied cash is paired with candidate invoices and proposed for approval.

    With Cash Application

  • Keep revenue schedules honest

    Subscription amendments made through orders are compared with invoice items. Changes that move recognized amounts are flagged with the order and the date.

    With Revenue Recognition

  • Renewal notice from the source

    Subscription term ends are read from the subscription record. The operator drafts a reminder for a person to send, and logs it.

    With Renewal Reminder

Requirements

  • A Zuora tenant and an administrator to create the API user and OAuth client
  • A dedicated API user with write access, as Zuora recommends for API and client library traffic
  • The base URL for your tenant and cloud, for example rest.sandbox.na.zuora.com, rest.apisandbox.zuora.com, or rest.test.zuora.com
  • Notification definitions with callout templates pointed at an HTTPS endpoint
Authentication
OAuth 2.0 client credentials: a client ID and secret created under Administration > Manage Users, exchanged at /oauth/token for a bearer token.

Limits

  • Rate limits are set per tenant: 50,000 API requests per minute on Production and Central Sandbox; 2,500 on API Sandbox
  • Concurrent requests are capped separately: 40 by default, 200 for high-volume transactions, 80 for Object Query
  • Exceeding a limit returns HTTP 429 with headers for remaining requests and reset time
  • A notification definition takes either eventCategory or eventTypeName, never both

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Zuora ↗

Questions and answers

How do I authenticate to the Zuora API?
With OAuth 2.0 client credentials. An administrator creates an API user and an OAuth client (client ID and secret) under Administration > Manage Users. You POST to /oauth/token and send the bearer token on each request.
What are the rate and concurrency limits?
Production and Central Sandbox allow 50,000 API requests per minute; Developer Sandbox 12,500; API Sandbox 2,500. Concurrent requests are limited separately: 40 by default, 200 for high-volume transactions, and 80 for Object Query. Exceeding either returns HTTP 429.
How do callouts work?
A notification definition pairs an event with a callout template. When the event occurs, Zuora makes an HTTP call to the URL in the template. Standard events use eventCategory; custom and custom scheduled events use eventTypeName. Histories can be queried and resent.
Ask about Zuora

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Zuora through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy