An org unit represents a business unit that operates independently and can sell products to multiple customers. Each org unit has its own isolated environment in which the org users can perform business operations independent of the other org units.

New field for account creation

organizationLabel: Specifies the name of the organization that the account belongs to.

New headers for data visibility

The following headers are supported for all Zuora public APIs and apply only when Multi-Org is enabled:

• Zuora-Org-Ids

• Zuora-Working-Org

These headers limit the data visibility for query APIs. The dataset that is returned is specific to the orgs specified in the headers.

The following query returns account data that is filtered based on the user's org labels and the Zuora-Org-Ids header:

POST/query/jobs
{
"query" : "select accountnumber, balance from account"
  ...
}

Depending on the user's org labels, Zuora-Org-Ids header, a different dataset would be returned for different scenarios:

Behavior of Zuora-Working-Org for creation APIs

Zuora-Working-Org will be used as the default org label value if the org label is not explicitly specified or there is no inheritance rule in place.

For example, to create a standalone invoice accountid is required. In this case, the invoice simply inherits the account org.

If there are no inheritance rules defined, the create action is labeled with the org specified by the Zuora-Working-Org header.

For example, to create an Account object through the Create Action call POST/v1/action/create the product will be labeled with the org specified in the Zuora-Working-Org header.

To see how all operations are supported for Multi-Org hierarchy management through REST API, see API Reference.