subscription.updated
subscription.updated is sent when a subscription was changed without changing its status: by the merchant in the panel or by the shopper themselves. What exactly is in changed, one of four values:
["quantity"]— units per charge (panel only);["interval_value", "interval_unit", "next_charge_at"]— the schedule: the interval and the next charge date are set together; a delivery skipped by the shopper arrives the same way —next_charge_atmoves out one interval, and undoing the skip moves it back to the skipped date;["delivery"]— the delivery address: it was changed for the subscription, or the shopper edited the saved address the subscription is on;["card"]— the shopper replaced the card themselves; the newbrandandmaskare in the snapshot’scard. The same replacement is accompanied by a 1 ₴payment.refundedwithorder_id: null.
The new values are in the snapshot; the event does not carry the previous ones. A status change is subscription.paused, subscription.resumed and subscription.cancelled; a price change is subscription.price_changed; a next_charge_at move after a payment is subscription.renewed. A cancelled subscription is not changed this way — it is activated first.
Event fields
Section titled “Event fields”| Field | Type | Description |
|---|---|---|
changed |
string[] | which snapshot fields changed: ["quantity"], ["interval_value", "interval_unit", "next_charge_at"], ["delivery"] or ["card"] |
The rest of data is the subscription snapshot.
Example
Section titled “Example”{ "id": "019a0b7c-1f3e-7c1a-9c6e-0b9b1c2d3e56", "event": "subscription.updated", "created_at": "2026-10-18T11:20:00+00:00", "shop_id": "7f3c2b1a-0d9e-4f8a-b7c6-d5e4f3a2b1c0", "data": { "id": "0199a1b3-5e6f-7a8b-9c0d-1e2f3a4b5c6d", "status": "active", "status_reason": null, "cancellation_reason": null, "product": { "id": "0199a1a0-2c3d-7e4f-8a5b-6c7d8e9f0a1b", "external_id": "SKU-1", "title": "Brit Care Adult Large Breed", "variant": "12 кг" }, "quantity": 2, "price": 249000, "discount_percent": 7, "interval_value": 4, "interval_unit": "week", "next_charge_at": "2026-11-01T09:00:00+00:00", "paused_until": null, "customer": { "id": "0199a1b5-1b2c-7d3e-8f4a-5b6c7d8e9f00", "first_name": "Олена", "last_name": "Коваль", "phone": "+380671234567", "locale": "uk" }, "delivery": { "provider": "nova-poshta", "type": "branch", "data": { "city": { "id": "…", "external_id": "8d5a980d-391c-11dd-90d9-001a92567626", "name": "Київ" }, "branch": { "id": "…", "external_id": "1ec09d88-e1c2-11e3-8c4a-0050568002cf", "name": "Відділення №1: вул. Пирогівський шлях, 135" } }, "recipient": { "first_name": "Олена", "last_name": "Коваль", "phone": "+380671234567" } }, "card": { "brand": "visa", "mask": "**** 4242" }, "created_at": "2026-10-04T09:12:30+00:00", "changed": [ "quantity" ] }}What to do
Section titled “What to do”- Overwrite only the fields listed in
changedin your system, taking the values from the snapshot; the rest of the snapshot may be refreshed too — it is complete. ["delivery"]— the new address applies from the next shipment; it does not change an already placed order of this subscription.["interval_value", …]— update the next charge date fromnext_charge_at, do not compute it yourself.
Related events
Section titled “Related events”subscription.price_changed— a price change is a separate eventsubscription.renewed—next_charge_atmoved by a payment, not by handsubscription.paused— status changes are separate events
Request headers, signature and retries are in the overview; the order of events is in the event flow.