POST /v1/subscriptions/{subscription-key}/preview
Describes how to preview an existing subscription to view information about existing and future invoices or credit memos.
Note: The zuora-version
parameter must be 207.0
or later.
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 |
---|---|---|---|
subscription-key |
String | Yes |
Subscription number or ID |
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 ( |
zuora-version |
String | No |
The minor version of the Zuora REST API. You need to set this parameter if you use the following fields:
If you have the Invoice Settlement feature enabled, you need to specify this parameter. Otherwise, an error is returned. |
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 |
---|---|---|---|
previewThroughDate |
Object | No |
The preview through date. |
previewThroughDate.nextBillingPeriods |
Number | No |
The number of billing periods to preview. Required if |
previewThroughDate.specificDate |
String | No |
The specific date for the preview start date. Required if |
previewThroughDate.previewThruDatePolicy |
String | No |
The options on how the preview through date is calculated.
Possible values:
|
previewStartDate |
Object | No |
The start date of the preview. |
previewStartDate.previewStartDatePolicy |
String | No |
The options on how the preview start date is calculated.
Possible values:
|
previewStartDate.specificDate |
String | No |
The specific date for the preview start date. Required if |
quantityForUsageCharges[] |
Array | No |
Container for usage charges. |
quantityForUsageCharges[].quantity |
Number | No |
The quantity of the subscription charge. |
quantityForUsageCharges[].chargeId |
String | No |
The ID of the subscription charge. |
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.