PUT /v1/orders/{orderNumber}/triggerDates
Note: This operation is only available if you have the Orders feature enabled. If you are an existing Zuora Subscribe and Amend customer, we recommend you enable Orders Harmonization to access the Orders feature. With Orders, you can access both existing functions for subscription and billing management and the new features on Zuora Billing.
Updates the triggering dates for either of the following order actions:
- CreateSubscription
- AddProduct
- UpdateProduct
- RemoveProduct
- RenewSubscription
- TermsAndConditions
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 |
---|---|---|---|
orderNumber |
String | Yes |
Order number of a pending order in which you are to update an order action's triggering dates. |
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. |
Zuora-Org-Ids |
String | No |
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. If the header is not set, the operation is performed in scope of the user's accessible orgs. |
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 |
---|---|---|---|
subscriptions[] |
Array | No | |
subscriptions[].orderActions[] |
Array | No | |
subscriptions[].orderActions[].triggerDates[] |
Array | No |
Container for the service activation and customer acceptance dates of the order action. |
subscriptions[].orderActions[].triggerDates[].name |
String | No |
Name of the trigger date of the order action. Possible values:
|
subscriptions[].orderActions[].triggerDates[].triggerDate |
String | No |
Trigger date in YYYY-MM-DD format. The date you are to set as the service activation date or the customer acceptance date. |
subscriptions[].orderActions[].sequence |
Integer | Yes |
Identifies which order action will have its triggering dates updated. |
subscriptions[].orderActions[].charges[] |
Array | No | |
subscriptions[].orderActions[].charges[].chargeNumber |
String | No |
Charge number of the charge which needs the triggering date to be provided. The charge's |
subscriptions[].orderActions[].charges[].specificTriggerDate |
String | No |
Date in YYYY-MM-DD format. The specific trigger date you are to set for the charge. |
subscriptions[].subscriptionNumber |
String | Yes |
Subscription number of a subscription in the |
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.