> This page is for Developers.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://zuora.ferndocs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://zuora.ferndocs.com/_mcp/server.

# Changelog

## May 26, 2026

## API updates

This section lists operations and fields that were added, changed, or removed.

The following API updates are available as of [Zuora Release 2026.Q2.0.2](https://docs.zuora.com/en/release-notes/latest-release).

* [Billing Documents](https://developer.zuora.com/v1-api-reference/api/billing-documents) - In the request body of the "Generate billing documents by account ID" operation, added the `commitmentKeys` field and updated the corresponding request sample.

* [E-Invoicing](https://developer.zuora.com/v1-api-reference/api/e-invoicing) - For each of the following operations, added the `transactionId` query parameter:
  * Sync the e-Invoice status of an invoice
  * Sync the e-Invoice status of a debit memo
  * Sync the e-Invoice status of a credit memo

## Doc updates

This section lists the documentation updates that were made in this version of the API Reference.

* In the request body of the "Generate billing documents by account ID" operation, corrected the `effectiveDate` and `targetDate` fields from optional to required.

* In the response body of each of the "Create a standalone invoice" and "Create standalone invoices" operations, added the missing nullable schema keyword to each of the following fields on the Invoice object:
  * `billToContactSnapshotId`
  * `soldToContactSnapshotId`
  * `lastEmailSentDate`
  * `postedBy`
  * `postedDate`
  * `transferredToAccounting`

* In the response body of each of the following operations, added the missing nullable schema keyword to each of the `billToContactId` and `billToContactSnapshotId` fields on the Debit Memo object:
  * Create debit memos
  * Create a debit memo from an invoice
  * Create a debit memo from a charge
  * Retrieve a debit memo
  * Update a debit memo
  * Update debit memos
  * Cancel a debit memo
  * Post a debit memo
  * Unpost a debit memo

* In the request body of the "Update invoices" operation, added the missing `No` enum value to the `invoices` > `transferredToAccounting` field.

* In the request and response body of the "Update an invoice" operation, added the missing `No` enum value to the `transferredToAccounting` field.

* In the request body of the "Update a payment run" operation, removed the incorrectly documented `date-time` format from the `runDate` field.

* Removed the incorrectly documented `date-time` format from each of the `createdDate` and `updatedDate` response fields across multiple operations.

## May 22, 2026

## API updates

This section lists operations and fields that were added, changed, or removed.

The following API updates are available as of [Zuora Release 2026.Q2.0.2](https://docs.zuora.com/en/release-notes/latest-release).

* [RSA Signatures](https://developer.zuora.com/v1-api-reference/api/rsa-signatures) - In the request body of the "Generate an RSA signature" operation, removed all unsupported fields and kept only the following supported fields:
  * `accountId`
  * `authorizationAmount`
  * `method`
  * `pageId`
  * `uri`

* [Custom Object Definitions](https://developer.zuora.com/v1-api-reference/api/custom-object-definitions) - Made the following updates to the "Update a custom object definition" operation for the support of request asynchronous processing:
  * Updated the operation description.
  * In the response body, added the `jobId` field.

* [Metadata](https://developer.zuora.com/v1-api-reference/api/Metadata/) - Added the following operations:
  * Retrieve metadata object schema
  * List available metadata objects

* [Settings](https://developer.zuora.com/v1-api-reference/api/settings) - Added the `defaultTemplate` field to the POST method request body of the `AllSummaryStatementTemplates` setting.

  See [200 response sample in JSON format](https://developer.zuora.com/settings-api/ListAllSettingsResponseSample.json).

## Doc updates

This section lists the documentation updates that were made in this version of the API Reference.

* Renamed the "Metadata" section in Deployment Manager to "Metadata Deployment" for better consistency.

* In the request body of each of the following operations, corrected the `On-Account Receivable` enum value to `OnAccountReceivable` for the `type` field:
  * Create an accounting code
  * Update an accounting code

* In the response body of the "Retrieve an accounting code" operation, corrected the `On-Account Receivable` enum value to `OnAccountReceivable` for the `type` field.

* In the response body of the "List all accounting codes" operation, corrected the `On-Account Receivable` enum value to `OnAccountReceivable` for the `accountingCodes` > `type` field.

* Updated the description of the "List all settings" operation to add the "Invoice Group" section.

## May 15, 2025

## API updates

This section lists operations and fields that were added, changed, or removed.

The following API updates are available as of [Zuora Release 2026.Q2.0.1](https://docs.zuora.com/en/release-notes/latest-release).

* [Invoices](https://developer.zuora.com/v1-api-reference/api/invoices/) - Added the "Cancel an invoice" operation.

* [Sequence Sets](https://developer.zuora.com/v1-api-reference/api/sequence-sets) - In the request body of the "Create sequence sets" operation, added the `sequenceSets` > `sequenceSetNumber` field.

## Doc updates

This section lists the documentation updates that were made in this version of the API Reference.

* In the response body of the "List payment methods of an account" operation, corrected the `returnedPaymentMethodType` > `creditCardMaskNumber` field to `returnedPaymentMethodType` > `cardNumber`.

* In the response body of the "Retrieve the default payment method of an account" operation, corrected the `creditCardMaskNumber` field to `cardNumber`.

* Removed the incorrectly documented `date-time` format description from all applicable fields across a number of operations.