The Generic API Loader application uses the Zuora APIs of Create, Update, and Delete in combination with CSV templates to perform mass requests. It enables you to create, update, and delete any Zuora object in bulk.
The Generic API Loader takes in a CSV file, reads through each line, performs the desired operation, and generates a results file and a failures file. If no error is encountered during the execution job, the failures file will be blank and the results file will report success statements for each line in the CSV. Otherwise, the lines are added to the failures file and each error is listed in the results file. This allows for an iterative approach where the failures file can be corrected based on the error received in the status file and re-uploaded as a new task.
Ensure that the "API Write Access" permission is enabled for your user role in the Zuora tenant.
Create a Generic API Loader Task
Take the following steps to create a task using the Generic API Loader:
- Navigate to New Task > Generic > API Loader.
- In the General tab, complete the following configuration:
- Enter the name of the task in the Name field.
- Select a run mode from the Run Mode drop-down list. See the Available Templates section below for more information.
- Create - Allows you to upload a CSV file where all columns are the API fields of the selected object in the Advanced tab. The Create requests will be executed for each row in the uploaded file.
- Delete - Allows you to upload a CSV file for mass deletions.
- Update - Allows you to upload a CSV file to update the information on the selected object in bulk.
- Select the timing of execution in the Execution drop-down list. The default execution is Onetime.
- Onetime - The task will be executed immediately when the resource is available.
- Scheduled - The task will be executed on the date and time specified in the schedule builder.
- (Optional) Select the build name in the Build Name drop-down list and the build version in the Version drop-down list if you want to run a task at a previous build version. The latest build name and version are populated by default. It is not recommended to update these fields because this could stop you from using the latest functionality built in the tool.
- Select the login to your Zuora tenant from the Target drop-down list or create a new login. Do not select the existing OAuth credentials or create new logins using OAuth because OAuth is not supported by Developer Tools.
- In the Advanced tab, complete the following settings:
- Select the object on which you want to operate from the Object drop-down list.
- Click Choose File and upload the CSV file that includes the desired API fields of the selected object.
Note: The SOAP API framework does not support localized number formats such as
1,234. Therefore, do not use thousand separators in SOAP requests. Use the standard numbering format such as
- (Optional) Select a value from the Max Threads and Max zObjects drop-down lists.
- Max Threads - Sets the number of threads that can be processed concurrently by the loader. The value for this field should not exceed Zuora's concurrent request limits. The default value is 3.
- Max zObjects - Sets the maximum number of the objects used in each call to Zuora. The default value is 50.
- If you selected Scheduled for the Execution field, complete the scheduler settings in the Schedule tab.
- Select the time zone from the Timezone drop-down list. Zuora strongly recommends you to select the same time zone as for your Zuora tenant to avoid payment errors.
- In the drop-down list next to Timezone, select the time frame of the schedule and complete the details of the selected time frame. The Timezone field and schedule builder are used to set how frequently the data is synchronized. It is recommended to set a Daily schedule and align the timezone to your Zuora tenant, which can align operations and ensure the app displays the latest data. The Interval field displays the specified schedules as a Cron expression and needs no further configuration.
- Click Create.
When configuring the Generic API Loader instance, you have to upload a CSV file for the selected operation. Note that if you are using Microsoft Excel on Mac OS, you must save the .csv file in MS-DOS Comma Separated (.csv) format.
Download Generic API Loader Sample Templates and the corresponding Generic API Loader Sample Template Data Dictionary to learn how to format the CSV file.
See the List of SOAP API Objects and click the object you want to operate on for more information about available fields and their descriptions that will help you format your CSV file.
The following limitations are applicable to Generic API Loader:
- When the Invoice Settlement feature is enabled for your tenant, Developer Tool defaults to the REST calls for the following objects:
- Credit Memo
- Debit Memo
Currently, only the fields in SOAP calls, and the fields in the REST calls to these objects can be updated.
Note that Generic API Loader only supports updating custom fields on the main objects listed above; it does not support updating custom fields on the sub items, such as Debit Memo Item.
- When creating a payment, only one debit memo item can be specified in the CSV file. Specifying multiple debit memo items is not supported yet.
- When updating the ProductRatePlanCharge object where the Tax feature is enabled, you must include the
TaxableCodefields in the CSV file.
- The files encoded with UTF-8 are supported, but encoded with UTF-8 with byte order mark (BOM) are not supported.