Zuora API Reference: Billing

Name: API Reference: Billing API
Brand: API Reference: Billing
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsBilling Subscriptionsnone428 EndpointsREST

For Agents

Programmatically list charge metrics by time range, list discount allocation details by time range. Covers 428 operations.

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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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

GET STARTED

Start building with API Reference: Billing API

Explore with Jentic

View OpenAPI Document

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

API Reference: Billing none credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'list charge metrics by time range') and Jentic returns the matching API Reference: Billing operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct API Reference: Billing integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.

Zuora API Reference: Billing

Connect the API Reference: Billing to your agent

Capabilities

Start building with API Reference: Billing API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs