Skip to content
Payments

zuora.com

Zuora sandbox and mock API

# 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 Referenc Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
428
Collections
-
Event types
-
example request
curl https://your-zuora.slurry.io/charge-metrics/data/charge-metrics \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 2021-08-20.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 428.

  • GET/charge-metrics/data/charge-metrics
  • GET/charge-metrics/data/charge-metrics-discount-allocation-detail
  • GET/events/event-triggers
  • POST/events/event-triggers
  • GET/events/event-triggers/{id}
  • PUT/events/event-triggers/{id}
  • DELETE/events/event-triggers/{id}
  • GET/notifications/email-templates
  • POST/notifications/email-templates
  • GET/notifications/email-templates/{id}
  • PUT/notifications/email-templates/{id}
  • DELETE/notifications/email-templates/{id}