Update a subscription
Update the editable fields of a subscription. Only the allow-listed properties may be changed; any other field is ignored. billing_address replaces the subscription’s billing address (all of street, house number, zip, city are required); the address row is mutated in place, so a row shared across a customer’s subscriptions changes everywhere it is referenced. payment_method attaches a new SEPA direct-debit mandate to the subscription, replacing the current mandate. metadata is merged key-by-key onto the stored metadata (a key set to null is removed; metadata: null clears every key). Returns the updated subscription.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
"sub_mi4f0oda6x9m7gcsvjk0ole1"
Body
The subscription fields to update
New billing address for the subscription
Attach a new SEPA direct-debit mandate. The new payment method replaces the subscription's current mandate.
Key-based metadata update. Keys sent here are merged onto the stored metadata; set a key to null to remove it. Send metadata: null to clear every key. Omit the field to leave the metadata unchanged. The resulting metadata is restricted to 10KB.
Response
The updated subscription
Type of the object, always 'subscription'
subscription Unique identifier for the subscription
"sub_rocbrf1u5e48mm0reeqoag90"
ID of the plan
"pln_ctj3tjzc7dywznuw1dy80lb3"
- Person
- Company
ID of the household the subscription belongs to. A household groups the contracts at one metering point: one consumption subscription at a time, plus the feed-in subscriptions on that same meter. It belongs to one customer and stays the same when they cancel and sign up again. A separately metered device, such as a heat pump with its own meter and consumption subscription, is a household of its own, so one customer at one address can have two.
"dom_k2m9x4qpz7w1c8v3n6b5t0ry"
Status of the subscription
pending, active, ended "active"
Estimated yearly usage in kWh, provided by the customer in the checkout.
2500
Timestamp when the subscription was created
"2024-03-14T12:00:00Z"
Timestamp when the subscription was updated
"2024-03-14T12:00:00Z"
Whether the subscription covers electricity consumption or feed-in. Feed-in subscriptions are only available from the 2026-05-27.curie API version onwards.
consumption, feed_in "consumption"
Human-readable identifier for the subscription
"4X44EMKX"
Timestamp when delivery was started / will start
"2024-03-14T12:00:00Z"
Timestamp when delivery was terminated
"2024-03-14T12:00:00Z"
Timestamp when the subscription was ended / will end
"2024-03-14T12:00:00Z"
Metadata of the subscription. Store any type of information, custom to your needs. E.g. the user_id of your in-house user. Restricted to 10KB.