PUT /v1/product-charge-definitions/{product-charge-definition-key}
Update a product charge definition.
Note: This operation requires the Attribute-based Pricing feature to be enabled, which is in the Early Adopter phase.
Servers
- https://rest.test.zuora.com
- https://rest.sandbox.na.zuora.com
- https://rest.apisandbox.zuora.com
- https://rest.na.zuora.com
- https://rest.zuora.com
- https://rest.test.eu.zuora.com
- https://rest.sandbox.eu.zuora.com
- https://rest.eu.zuora.com
Path parameters
Name | Type | Required | Description |
---|---|---|---|
product-charge-definition-key |
String | Yes |
The unique number or ID of the product charge definition to be updated. |
Request headers
Name | Type | Required | Description |
---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Content-Encoding |
String | No |
Include the |
Zuora-Track-Id |
String | No |
A custom identifier for tracing the API call. If you set a value for this header, Zuora returns the same value in the response headers. This header enables you to associate your system process identifiers with Zuora API calls, to assist with troubleshooting in the event of an issue. The value of this field must use the US-ASCII character set and must not include any of the following characters: colon ( |
Authorization |
String | No |
The value is in the |
Zuora-Entity-Ids |
String | No |
An entity ID. If you have Zuora Multi-entity enabled and the OAuth token is valid for more than one entity, you must use this header to specify which entity to perform the operation in. If the OAuth token is only valid for a single entity, or you do not have Zuora Multi-entity enabled, you do not need to set this header. |
Accept-Encoding |
String | No |
Include the If specified, Zuora automatically compresses responses that contain over 1000 bytes of data, and the response contains a |
Request body fields
Name | Type | Required | Description |
---|---|---|---|
defaultQuantity |
Number | No |
The default quantity. This field is applicable only for one-time and recurring charges. |
billingPeriod |
String | No |
The override value of the billingPeriod for the product charge definition. |
prices[] |
Array | No |
Container for the new prices to override the existing prices of the product charge definition. |
prices[].price |
Number | No |
The price of this item. This field is only applicable for charges based on the following charge models:
|
prices[].tiers[] |
Array | No |
Container for the tiers of the price item. This field is only applicable for charges based on the following charge models:
You must specify all relevant fields of all tiers, including pricing information for each currency.
For each currency, ensure that the tiers appear in ascending order of For example:
|
prices[].discountPercentage |
Number | No |
The percentage of discount for a percentage discount. The field is applicable only for charges based on the Discount-Percentage charge model. |
prices[].currency |
String | No |
The currency for the price. |
prices[].discountAmount |
Number | No |
The specific amount for a fixed discount. The field is applicable only for charges based on the Discount-Fixed Amount charge model. |
uom |
String | No |
Describes the unit of measure (UOM) configured in Settings > Billing. Values: |
chargeModel |
String | No |
Determines how to calculate charges. Charge models must be individually activated in Zuora Billing administration. Possible values:
|
listPriceBase |
String | No |
The list price base. This field is applicable only for recurring charges. Note: The Possible values:
|
effectiveStartDate |
String | No |
The effective start date of the product charge definition. |
specificListPriceBase |
Integer | No |
The number of months for the list price base of the charge definition.
The field is |
specificBillingPeriod |
Number | No |
The override value of the specificBillingPeriod for the product charge definition. |
effectiveEndDate |
String | No |
The effective end date of the product charge definition. |
termType |
String | No |
The type of the subscription that is eligible for this charge definition. Possible values:
|
term |
Number | No |
The number of periods of a termed subscription that is eligible for this charge definition. This field is applicable when the |
billingTiming |
String | No |
The override value of the billingTiming for the product charge definition. Possible values:
|
taxCode |
String | No |
Specifies the tax code for taxation rules. This field is equired when the Note: This value affects the tax calculation of the charge. |
taxMode |
String | No |
Determines how to define taxation for the charge. This field is equired when the Note: This value affects the tax calculation of the charge. Possible values:
|
taxable |
Boolean | No |
Determines whether the charge definition is taxable. When this field is set to Character limit: 5 Values: Note: This value affects the tax calculation of the charge. |
termPeriodType |
String | No |
Specifies the period type for the subscription term that is eligible for this charge definition. Possible values:
|
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.