Discussions

Context
When creating a yearly subscription with 1 occurrence via the API, the start date is set to the subscription creation date, but the end date returned is also that same date.
In the Pennylane interface, however, it is possible to define an end date that is consistent with the subscription duration (for example start + 1 year for a yearly subscription). The behaviour is therefore not identical between the interface and the API.

Problem

• Via the API, it is not possible to configure the end date (“finish”) when creating a subscription, whereas this information is available and manageable in the interface.

• For a yearly subscription with a single occurrence, having an end date equal to the start date does not reflect the actual contractual duration.

• This makes it harder to automatically identify “ended” subscriptions (one‑year period elapsed) vs “active” subscriptions (period still ongoing), especially when all subscriptions are created via the API only.

Impacted endpoints/schema

• POST /api/external/v2/billing_subscriptions

• The “finish” field is present in the response, but it is neither configurable in the creation payload nor automatically computed in a way that is consistent with the subscription duration, unlike what is possible in the interface.