Update
Updates a subscription’s extra_data, price, components, offer and cancel_reason.
Only the Application API Scope can change price, components and offer. With the Storefront API Scope those fields are ignored: the request returns 200 and leaves them unchanged.
New bundle components can’t be changed here: for a subscription to a static or dynamic price bundle, sending components returns 422. Use Update Components instead.
Authentication
Application API Scope — server-to-server, sent in the x-api-key header. See Authentication.
Path parameters
Request
JSON object that should be JSON.parse() as key/value store for any extra information.
Price, must be in decimal form ex: 10.00
Array of JSON objects to set product IDs that are the legacy bundle components. For example: “components”: [ {“product”:“123”}, {“product”:“456”}, {“product”:“789”} ],
Pipe-delimited cancel reason code and cancel reason details, e.g. “4|Overstocked”
Response
The subscription type as stored. subscription_type reports IU replenishment and CSA replenishment as replenishment; this field keeps the original value.
Bundle components. Each has product; public_id and quantity are returned only when the merchant has multi-item bundles enabled.
Custom data stored on the subscription, as a JSON object. {} when the subscription has none. Ordergroove and your integrations can store their own keys here.
Three-letter ISO currency code.
Pending queued actions, in order. Returned only when the merchant has queued actions enabled; empty when the subscription isn’t live or has none.
Prepaid details. Returned only when the merchant has prepaid subscriptions enabled; null when this subscription isn’t prepaid.
Present only if the subscription has a free trial context (i.e. it was created for a product with a free trial configured); omitted otherwise.