> For the complete documentation index, see [llms.txt](https://docs.digitalriver.com/commerce-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalriver.com/commerce-api/shopper-apis/subscriptions/update-subscription-at-the-next-renewal/changing-the-subscription-renewal-quantity.md).

# Changing the subscription renewal quantity

Managing your Digital River subscription services is crucial for maintaining customer satisfaction and streamlining your operations. One key aspect of subscription management is adjusting the renewal quantity based on customer needs or inventory levels. This guide will walk you through the simple yet powerful process of updating the renewal quantity for any subscription. Whether you're scaling a customer's service up or down, this functionality ensures that your subscriptions remain flexible and responsive to changes in demand.

Understanding why a shopper might want to adjust their renewal quantity can guide your approach to subscription management and customer service. Here are the key reasons:

* **Changing needs**: A shopper's need for your product or service could change over time, requiring adjustments to their subscription quantity.
* **Financial planning**: Shoppers may adjust their renewals based on budget considerations, opting for more or fewer services or products as their financial situation changes.
* **Operational adjustments**: For businesses, operational changes might necessitate more or fewer subscriptions.
* **Expanding or downsizing**: As a shopper's business grows or scales down, they may need to adjust their subscription correspondingly.
* **Optimizing resources**: Shoppers might discover they are over or under-utilizing a service and adjust their subscription to match their actual usage.

Understanding these reasons will help you better manage your subscription services and align them with your dynamic business needs.

To change the subscription renewal quantity, send a [`POST /v1/subscriptions/{subscriptionId}/renewal-quantity`](https://docs.digitalriver.com/commerce-api-references/shopper-apis/subscriptions/manage-the-subscriptions-renewal-plan#v1-subscriptions-subid-renewal-quantity) request. You must replace `{subscriptionId}` with the actual ID of the subscription you wish to modify and specify the desired `renewalQuantity` in the request's body. 

In the following example, the value for the `renewalQuantity` is `2`.

{% tabs %}
{% tab title="cURL" %}

```javascript
curl --location --request POST 'https://api.digitalriver.com/v1/subscriptions/{subscriptionId}/renewal-quantity' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer ***' \
--data-raw '{
"renewalQuantity": 2
}'
```

{% endtab %}
{% endtabs %}

After submitting the request, you should receive a `202 Accepted` response, indicating that the request to change the renewal quantity has been accepted and will be processed. The new plan will go into effect on the next renewal.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.digitalriver.com/commerce-api/shopper-apis/subscriptions/update-subscription-at-the-next-renewal/changing-the-subscription-renewal-quantity.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.