# Zuora Data Labeling API

**Canonical:** https://apis.io/apis/zuora/zuora-data-labeling-api/  
**Provider:** Zuora — https://apis.io/providers/zuora/  
**Documentation:** https://developer.zuora.com/v1-api-reference/introduction

Zuora Data Labeling API is one of 80 APIs that [Zuora](https://apis.io/providers/zuora/) publishes on the [APIs.io](https://apis.io/) network, described by a machine-readable OpenAPI specification. Tagged areas include Data Labeling. The published artifact set on APIs.io includes an OpenAPI specification.

The Data Labeling APIs help you to label your existing data with organization(s) in Zuora. Once you turned on Multi Org feature, if you don't label your existing data, they are simply unlabeled, and unlabeled data can be accessed by all organizations in your tenant. To limit the access of your existing data, you need to label them with organization(s) you defined in the organization hierarchy management setting page. Once labeled, the data can only be accessed by users who have been granted with the labeled organization(s). Note that you have to enable the "Multi Org" feature before using the Data Labeling APIs. ### General guidelines * Firstly, create the org hierarchy and determine the data categorization strategy, for example, by currency, by region, by custom fields etc. * You have to migrate all customer accounts before labeling products in the product catalog * You can leave the users at the root, just so long as you understand that the user would have access to all the Org Units within the Multi-org enabled tenant * Currently, you need to manually label existing Journal Runs, JournalEntry, and AccountingPeriod objects by editing, tell us your use case if you want to automate this process. ### Order of object labeling Except for `Account` and `Product`, there are no dependencies between objects, users can label them in parallel. But please keep in mind that the data access control ensues from the object labeling. For example, if you label a scheduled `BillRun` with `US` org, when it's triggered next time, the bill run will only pick up customer accounts of the `US` org, not others. Likewise, labeling a user will change the user's visible data scope, for example, an `EU` user won't be able to see `US` accounts anymore.

## Machine-readable artifacts (1)

- **OpenAPI** — https://raw.githubusercontent.com/api-evangelist/zuora/refs/heads/main/openapi/zuora-data-labeling-api-openapi.yml

## Other Zuora APIs (12)

- [Zuora V1 API](https://apis.io/apis/zuora/v1-api/)
- [Zuora Accounting Codes API](https://apis.io/apis/zuora/zuora-accounting-codes-api/)
- [Zuora Accounting Periods API](https://apis.io/apis/zuora/zuora-accounting-periods-api/)
- [Zuora Accounts API](https://apis.io/apis/zuora/zuora-accounts-api/)
- [Zuora Actions API](https://apis.io/apis/zuora/zuora-actions-api/)
- [Zuora Aggregate Queries API](https://apis.io/apis/zuora/zuora-aggregate-queries-api/)
- [Zuora API Health API](https://apis.io/apis/zuora/zuora-api-health-api/)
- [Zuora Attachments API](https://apis.io/apis/zuora/zuora-attachments-api/)
- [Zuora Bill Run API](https://apis.io/apis/zuora/zuora-bill-run-api/)
- [Zuora Bill Run Health API](https://apis.io/apis/zuora/zuora-bill-run-health-api/)
- [Zuora Billing Documents API](https://apis.io/apis/zuora/zuora-billing-documents-api/)
- [Zuora Billing Preview Run API](https://apis.io/apis/zuora/zuora-billing-preview-run-api/)

## Tags

Data Labeling

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/apis/zuora/zuora-data-labeling-api/). The API's provider profile, Kin Score and agent-readiness rating are at https://apis.io/providers/zuora/.