{"templateId":"api_docs","sharedDataIds":{"apiDocsStore":"api-docs-other-api/revenue-api-3.0.yaml","sidebar":"sidebar-other-api/sidebars.yaml"},"props":{"definitionId":"other-api/revenue-api-3.0.yaml","settings":{"baseUrlPath":"/other-api/revenue-api-3.0"},"disableAutoScroll":true,"seo":{"title":"Revenue API Reference"},"dynamicMarkdocComponents":[],"metadata":{"type":"openapi","title":"Revenue API Reference","version":"2026-10-16","description":"\n# Introduction\n\n\nWelcome to the reference for Zuora Revenue REST API!\n\n\nREST is a web-service protocol that lends itself to rapid development by \nusing everyday HTTP and JSON technology. Zuora Revenue provides various REST \nAPIs for data integration. Use these REST APIs to authenticate and integrate \ndata from the source ERP systems with Zuora Revenue.\n\n\nAll Zuora Revenue REST APIs are secured by using HTTPS. The authentication scheme is token-based authentication, \nwhich means an authenticated user must generate a token and then use it for all subsequent APIs until the token expires.\n\n\nThis reference provides detailed descriptions about functions, requests, and responses of each REST API.\n\nZuora Revenue REST APIs can be broadly classified into the following categories:\n\n * Authentication\n\n * Inbound\n\n * Outbound \n \n**Remember:** \n\n\n * The API service must be enabled for your tenant in the first place. Otherwise, the 405 error will be returned for every API request you submitted. To enable the API service, contact Zuora Revenue Support.\n\n * Both the inbound and outbound operations require an authentication token to perform integration.\nYou can obtain the token by using the Authentication operation.\n\n\n## Endpoints\n\nAfter the APIs are provisioned in Zuora Revenue Cloud, you can get the endpoint and use that endpoint to call the APIs.\n\n\n\n## Requirements\n\nBefore you use the Zuora Revenue APIs, make sure the following requirements are met:\n\n  * Zuora Revenue uses role based access control to restrict system access to authorized users. \nTo use the Zuora Revenue APIs, make sure that your user role has the **Webservices Inbound** \nand **Webservices Outbound** previleges in Zuora Revenue security settings. For more information, \nsee <a href=\"https://docs.zuora.com?resourceId=revenue-user-mgmt-access\" target=\"_blank\">Manage User Access</a>.      \n  * To use the inbound operations to upload data into Zuora Revenue, the upload templates must be created by using the **File Upload** menu options in the Zuora Revenue UI. \n  Currently, the APIs support transaction upload, bundle upload, and event upload.\n  * To use the outbound operations, the outbound GL interface mapping must be set up in the Zuora Revenue UI (**Setups > Application > Interface Setup**). \n\n\n## Requests and Responses\n\nZuora Revenue APIs support the JSON format of HTTP responses. Inbound operations for data upload support the CSV format only.\n\n\n## Inbound Data Error\n\nAll the inbound data into Zuora Revenue are first loaded into pre-stage tables, namely CUST_UI tables in Zuora Revenue,\nand then pushed to the corresponding staging tables from CUST_UI tables. \n\n\nIf the data fails in the CUST_UI tables, the entire batch of records will be marked as `Failed`.\nIt means All or Nothing approach will be followed when data is being inserted to the CUST_UI tables. \nIf the data has been successfully inserted into the CUST_UI tables, it will then be automatically pushed to \nthe staging tables and no manual work is required. \n\n\nAny uncollected data that remains in the staging tables can be manually fixed or downloaded, and can be reposted from the upstream systems. \n\n\nYou can use the Stage Error operations to retrieve error information about the uploaded data.\n"},"compilationErrors":[],"markdown":{"partials":{},"variables":{"rbac":{"teams":["anonymous"]},"user":{},"remoteAddr":{"hostname":"developer.zuora.com","port":4000,"ipAddress":"216.73.216.90"},"lang":"default_locale","env":{"PUBLIC_REDOCLY_BRANCH_NAME":"main"}}},"pagePropGetterError":{"message":"","name":""}},"slug":"/other-api/revenue-api-3.0","userData":{"isAuthenticated":false,"teams":["anonymous"]},"isPublic":true}