SubscriptionType
A subscription type: the organisation's hand-maintained template a customer subscription is instanced from, carrying the default billing interval and renewal behaviour new subscriptions start with.
- Summary view
- SubscriptionTypeList, 12 fields. What a list returns by default.
- Detail view
- SubscriptionType, 12 fields. The default for a single read and for every write.
Its template lines live on the items sub-resource, and the type's name is the name plnnrly shows for every subscription of that type.
Used by
/subscription-types/{subscription_type}/actions/restoreSubscriptionTypeFields
- Detail only
- Only in the detail view.
- Only with include
- Only when you ask for it with include.
- Server-assigned
- Set by plnnrly, never by a request.
Subscription type name. It is also the name every customer subscription of this type is displayed under, so renaming a type renames what its existing subscriptions read as. Names are not unique.
Interval a new subscription of this type is billed at by default. Omitting it on create yields yearly, the stored default, not the monthly that plnnrly's form pre-selects, which is a form convenience the API deliberately does not reproduce.
yearlymonthlyone-time
New values may be added.
Whether subscriptions created from this type renew automatically by default. The value is stored exactly as sent; nothing forces it to false.
Whether the type is offered in the catalogue. It is a catalogue flag only: nothing in the application filters on it, so deactivating a type does not stop existing subscriptions of that type from being renewed or invoiced.
Position in the catalogue, assigned by the server on create as one past the highest existing position. It is the default sort key, and there is no way to reorder types through the API: dragging types into order in plnnrly has no API equivalent in v2.0.
Last-write timestamp; use for incremental sync. It also feeds the ETag revision, because a subscription type has no version field.
Variants
SubscriptionTypeList 12 fields
What a collection returns, and what ?view=summary returns on a single record.
The same fields as the detail object.
SubscriptionTypeSummary 2 fields
The embedded form: what you get when another resource carries this one and you did not include it.
Leaves out: description, default_billing_interval, auto_renew, active, sort_order, created_at, updated_at, deleted_at, items_count, links
SubscriptionTypeLinks 2 fields
The links object on this resource.
Keys: self, items
Something wrong or missing on this page? Tell us