The Prepaid with Drawdown feature is a pricing model for consumption-based services, such as data storage. Under this model, customers pay upfront to receive a number of units, usually for a period of time like a month or a year. Then they consume against that prepayment balance in a use-it-or-lose-it fashion, with a possibility of topping up more units or being charged for any overage. This model strikes a balance between upfront commitment and the pure pay-as-you-go pricing models. For more information, see Prepaid with Drawdown.
This REST API reference describes how to manually reverse fund rollover from source validity period to destination validity period. There are no path or query parameters.
Note: This API will not work if the associated prepayment charge has rollover enabled.
Specify a unique idempotency key if you want to perform an idempotent POST or PATCH request. Do not use this header in other request types.
With this header specified, the Zuora server can identify subsequent retries of the same request using this value, which prevents the same operation from being performed multiple times by accident.
Include the Accept-Encoding: gzip header to compress responses as a gzipped file. It can significantly reduce the bandwidth required for a response.
If specified, Zuora automatically compresses responses that contain over 1000 bytes of data, and the response contains a Content-Encoding header with the compression algorithm so that your client can decompress it.
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 should not set this header.
Comma separated IDs. If you have Zuora Multi-Org enabled, you can use this header to specify which orgs to perform the operation in. If you do not have Zuora Multi-Org enabled, you should not set this header.
The IDs must be a sub-set of the user's accessible orgs. If you specify an org that the user does not have access to, the operation fails. This header is important in Multi-Org (MO) setups because it defines the organization context under which the API should operate—mainly used for read access or data visibility filtering. If the header is not set, the operation is performed in scope of the user's accessible orgs.
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 (:), semicolon (;), double quote ("), and quote (').
The minor API version.
For a list of available minor versions, see API upgrades.
Date range of the destination validity period to which the funds are transferred. It should be close to the source validity period.
{ "endDate": "2024-01-01", "startDate": "2023-01-01" }
Specifies the units of measure for prepayment charge. Units of measure are configured in the web-based UI. Your values depend on your configuration in Billing Settings.
Values: a valid unit of measure
Date range of the source validity period from which the funds are transferred. It should be close to the destination validity period.
{ "endDate": "2025-01-01", "startDate": "2024-01-01" }
- https://rest.test.zuora.comhttps://rest.test.zuora.com/v1/ppdd/reverse-rollover
- US API Sandbox Cloud 1https://rest.sandbox.na.zuora.com/v1/ppdd/reverse-rollover
- US API Sandbox Cloud 2https://rest.apisandbox.zuora.com/v1/ppdd/reverse-rollover
- US Production Cloud 1https://rest.na.zuora.com/v1/ppdd/reverse-rollover
- US Production Cloud 2https://rest.zuora.com/v1/ppdd/reverse-rollover
- https://rest.test.eu.zuora.comhttps://rest.test.eu.zuora.com/v1/ppdd/reverse-rollover
- EU API Sandboxhttps://rest.sandbox.eu.zuora.com/v1/ppdd/reverse-rollover
- EU Productionhttps://rest.eu.zuora.com/v1/ppdd/reverse-rollover
- https://rest.test.ap.zuora.comhttps://rest.test.ap.zuora.com/v1/ppdd/reverse-rollover
- APAC Productionhttps://rest.ap.zuora.com/v1/ppdd/reverse-rollover
{ "destinationValidityPeriod": { "endDate": "2024-01-01", "startDate": "2023-01-01" }, "prepaymentUom": "Each", "sourceValidityPeriod": { "endDate": "2025-01-01", "startDate": "2024-01-01" }, "subscriptionNumber": "A-S00000009" }
OK
This header is returned if you specify the Accept-Encoding: gzip request header and the response contains over 1000 bytes of data.
Note that only the following MIME types support gzipped responses:
application/jsonapplication/xmltext/htmltext/csvtext/plain
The request limit quota for the time window closest to exhaustion. See rate limits for more information.
The number of requests remaining in the time window closest to quota exhaustion. See rate limits for more information.
The number of seconds until the quota resets for the time window closest to quota exhaustion. See rate limits for more information.
The Zuora internal identifier of the API call. You cannot control the value of this header.
A custom identifier for tracing the API call. If you specified a tracing identifier in the request headers, Zuora returns the same tracing identifier. Otherwise, Zuora does not set this header.
The type of the concurrency limit, which can be Default, High-volume transactions, or Object Query.
For more information, see Concurrent request limits.
The total number of the permitted concurrent requests.
For more information, see Concurrent request limits.
The remaining number of the permitted concurrent requests.
For more information, see Concurrent request limits.
{ "message": "Reverse rollover is done", "reverseRolloverFundCount": 1, "success": true }