Prerequisites
Slicker integrates with Zuora via Zuora’s Quickstart API. To use the Quickstart API, your Zuora tenant must have the following features enabled: Only Zuora users with the appropriate permissions can create API credentials - the tenant administrator can grant these permissions and can create API credentials.Create credentials
Zuora API authentication requires an OAuth client ID and secret. You should follow the official Zuora documentation to create these credentials. Some points to note:- The User Role should have
API Write Rolepermissions. This is required for Slicker to retry failed transactions and recover revenue. In addition, the following specific permissions must be enabled on the role:- Process Electronic Payment (Payments Roles) — needed to trigger payment collection on invoices, which is core to how Slicker recovers failed payments.
- Change Payment Methods (Billing Roles) — needed to temporarily disable Zuora’s built-in retry rules on a payment method so that Slicker controls the retry timing during an experiment, and then re-enable them afterwards.
- Modify Invoice (Billing Roles) — needed to set custom fields on invoices for experiment tracking.
- Make sure that the
UI Accessbox is unchecked. Zuora recommends API credentials are never used for UI access. - Copy the
Client IDandClient Secret- we will need them later.
Create integration in Slicker
- Go to the Slicker’s new integration page.
- Select
Zuorafrom the list of integrations. - Give the integration a name and description to help you identify it later.
- Enter the Client ID and Secret you copied earlier.
- Select the base URL of your tenant from the dropdown. This is based on the data center where your Zuora tenant is hosted as detailed in Zuora’s documentation.
- Click the
Submitbutton to create the integration.
Troubleshooting
On integration creation, Slicker will attempt to connect to Zuora using the provided API key. If the connection fails, you will see an error message like the one below. Please double-check the API key, make sure it has the correct permissions, and try again.