# Remove scheduled subscription changes

### Parameters <a href="#parameters" id="parameters"></a>

| Parameters                                                                                                                                                                                                                                                                | Type/Description                      |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------- |
| `sessionID`                                                                                                                                                                                                                                                               | <p><strong>Required (String)</strong> |
| <br>Session identifier, the output of the <strong>Login</strong> method. Include <strong>sessionID</strong> into all your requests. 2Checkout throws an exception if the values are incorrect. The <strong>sessionID</strong> expires in <strong>10 minutes</strong>.</p> |                                       |
| `SubscriptionReference`                                                                                                                                                                                                                                                   | <p><strong>Required (String)</strong> |
| <br>The system-generated reference code of the subscription.</p>                                                                                                                                                                                                          |                                       |

### Response <a href="#response" id="response"></a>

| Parameters | Type/Description                                                               |
| ---------- | ------------------------------------------------------------------------------ |
| `Boolean`  | **True** or **False** depending on whether the changes were successful or not. |

### Request <a href="#request" id="request"></a>

```php
<?php

require('PATH_TO_AUTH');

$subscriptionReference = 'YOUR_SUBSCRIPTION_REFERENCE';

$jsonRpcRequest = [
    'method' => 'removeScheduledProductUpdate',
    'params' => [$sessionID, $subscriptionReference],
    'id' => $i++,
    'jsonrpc' => '2.0'
];

var_dump(callRPC((object)$jsonRpcRequest, $host, true));
```

### FAQ: <a href="#faq__003a" id="faq__003a"></a>

<details>

<summary>When is the scheduled update applied?</summary>

At the next renewal - for both auto-renewals and manual renewals.​

</details>

<details>

<summary>Is there a limit on how far in advance I can schedule an update?</summary>

No specific time limit is enforced - the update remains scheduled until the next renewal or until explicitly removed.​

</details>

<details>

<summary>How late in the billing cycle can an update be scheduled?</summary>

At any point during the billing cycle, right up until the renewal.​

</details>

<details>

<summary>Can I schedule changes to product, pricing options, and quantity at the same time?</summary>

Yes. ProductCode, PricingOptions, and Quantity can be combined in a single scheduling call.​

</details>

<details>

<summary>Can I schedule a quantity decrease?</summary>

Yes. A quantity decrease is supported, but Quantity = 0 and negative values are not allowed and will return validation errors.​

</details>

<details>

<summary>Are all pricing option types supported for scheduled subscription changes? </summary>

Yes, with one exception: pay-per-usage (PAYPERUSAGE) pricing options are not supported.​

</details>

<details>

<summary>Where can I see the scheduled update?</summary>

In the GET subscription response under Future Events, and in the license history in the Control Panel and MyAccount after the update is applied.​

</details>

<details>

<summary>Are shoppers notified when a subscription change is scheduled?</summary>

No. Scheduling a subscription change does not trigger a notification to the shopper, however, an LCN will be sent to the vendor who can then decide to notify the shopper.​

</details>

<details>

<summary>Does the renewal price reflect the scheduled changes?</summary>

Yes. The GET renewal price APIs return pricing based on the scheduled changes.​

</details>

<details>

<summary>Is the scheduled update applied if the subscription is renewed manually via MyAccount?</summary>

Yes. The scheduled update is respected across all renewal paths.​

</details>

<details>

<summary>Does an existing coupon still apply after a scheduled product change? </summary>

Yes, provided the coupon is compatible with the new product. If the coupon is not compatible with the product being updated to, it will not be applied after the change.​

</details>

<details>

<summary>Does an early renewal honor the scheduled changes? </summary>

Yes. Early renewals respect the scheduled update - the subscription will renew with the new product, pricing options, and/or quantity as defined in the scheduled change.​

</details>

<details>

<summary>Is bulk scheduling across multiple subscriptions supported? </summary>

No. Scheduling is performed per individual subscription reference. Bulk scheduling across multiple subscriptions in a single API call is not supported — the API is designed specifically for one subscription at a time.

</details>

&#x20;

&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.2checkout.com/json-rpc-api-reference/json-rpc-api-6.0/api-requests/subscription/remove-scheduled-subscription-changes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.