Zuora API Reference: Billing
Community OpenAPI document · agent-readyPaymentsBilling Subscriptionsnone428 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically list charge metrics by time range, list discount allocation details by time range. Covers 428 operations.
Use for: I need to charge metrics by time range, I want to discount allocation details by time range, Search for an event trigger, Find all event triggers
Not supported: Does not handle communications, crm, or developer tools - use for payments only.
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: . The API exposes 428 endpoints.
Install Jentic One Beta
Connect the API Reference: Billing to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API Reference: Billing, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fzuora.com%2Fzuora" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fzuora.com%2Fzuora" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with API Reference: Billing API.
List charge metrics by time range
Create an event trigger
Retrieve an event trigger
Update an event trigger
Delete an event trigger
Use Cases
Patterns agents use API Reference: Billing API for, with concrete tasks.
★ Payments Operations
Use the API Reference: Billing to perform payments operations programmatically. The API provides 428 endpoints covering core functionality including list charge metrics by time range, list discount allocation details by time range, create an event trigger.
Call GET /charge-metrics/data/charge-metrics to list charge metrics by time range
Automated Actions Management
Automate actions operations by combining multiple API Reference: Billing endpoints. Agents can list discount allocation details by time range and then create an event trigger in a single workflow.
Call GET /charge-metrics/data/charge-metrics-discount-allocation-detail to list discount allocation details by time range, then verify the result
AI Agent Integration via Jentic
AI agents discover and call API Reference: Billing endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.
Search Jentic for 'list charge metrics by time range', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
428 endpoints — 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.
METHOD
PATH
DESCRIPTION
GET
/charge-metrics/data/charge-metrics
List charge metrics by time range
GET
/charge-metrics/data/charge-metrics-discount-allocation-detail
List discount allocation details by time range
POST
/events/event-triggers
Create an event trigger
GET
/events/event-triggers
List event triggers
GET
/events/event-triggers/{id}
Retrieve an event trigger
PUT
/events/event-triggers/{id}
Update an event trigger
DELETE
/events/event-triggers/{id}
Delete an event trigger
POST
/notifications/email-templates
Create an email template
GET
/charge-metrics/data/charge-metrics
List charge metrics by time range
GET
/charge-metrics/data/charge-metrics-discount-allocation-detail
List discount allocation details by time range
POST
/events/event-triggers
Create an event trigger
GET
/events/event-triggers
List event triggers
GET
/events/event-triggers/{id}
Retrieve an event trigger
PUT
/events/event-triggers/{id}
Update an event trigger
DELETE
/events/event-triggers/{id}
Delete an event trigger
POST
/notifications/email-templates
Create an email template
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Zuora Billing by hand means configuring its authentication, pointing at the rest.zuora.com host, and handling billing-object pagination yourself. Through Jentic you install once, import Zuora Billing from the API Directory, store the credential once, and your agent calls it.
Permission scoping
Zuora puts the event trigger id in the URL path (/events/event-triggers/{id}), so a rule can pin your agent to one event trigger: it can read and update that trigger and nothing else. You choose the operations it may call, so destructive ones like deleting an event trigger are not included unless you add them.
Credential isolation
Your Zuora credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list charge metrics by time range' or 'create an email template', and Jentic returns the matching Zuora Billing operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Alternative payments API
Choose Stripe when you need a different approach to payments operations
FAQs
Specific to using API Reference: Billing API through Jentic.
What authentication does the API Reference: Billing use?
The API Reference: Billing uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I list charge metrics by time range with the API Reference: Billing?
Yes. Use the GET /charge-metrics/data/charge-metrics endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the API Reference: Billing?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I list charge metrics by time range through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list charge metrics by time range'. Jentic returns the matching API Reference: Billing operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the API Reference: Billing have?
The API Reference: Billing exposes 428 endpoints covering actions, accounting codes, accounting periods operations.
Can I limit what my agent is allowed to do with the Zuora Billing API?
Yes. Because you run Jentic One yourself, your own rules decide which Zuora Billing operations and credentials the agent may use. Since Zuora carries the event trigger id in the URL path (/events/event-triggers/{id}), you can pin the agent to a single event trigger so it only reads and updates that one and touches nothing else. You choose the operations it may call, so destructive ones like deleting an event trigger stay off unless you add them.
GET STARTED