List subscription types
GEThttps://
Returns the organisation's subscription types in catalogue order: sort_order ascending, the same order plnnrly shows.
Access
- Token scope
- api:
read: subscription_types Without it:
403 insufficient-token-scope. - Permission
- subscription_types::
read Without it:
403 insufficient-permission. - Feature
- Needs the billing feature on your organisation.
Without it:
404 endpoint-not-found. - Rate cost
- 1 unit, read bucket.
view=detailmakes it 3. Adds:q+2. - Also
If-None-Matchanswers304when nothing changed. Never cached:private, no-store. Unknown query parameters are refused, never ignored.
Both are checked, scope first. A token never does more than its user. How access is checked
Defaults to the summary view; view=detail carries the same fields on this resource (no field of it is detail-only) and costs three read units instead of one. Search with q= over the type name, and pass trashed=with|only to see deleted types.
Query parameters
Unknown parameters are refused with 400, naming the parameter.
18 parameters in 6 groups
Views
Pagination
Rows per page. At most 25 when include names a to-many relation; a larger value is 400 invalid-query-parameter.
Default: 25
Opt in to page-number paging: 1-based, at most 1000. Omit it, the default, to page by opaque cursor, which is what links.next hands you. Cannot be combined with cursor. Published only on collections that count their rows on every request. This collection's default sort is a display position that changes whenever someone drags the list into a new order in plnnrly, so a page number can skip or repeat a row if the list is reordered between two page requests. These collections rarely exceed one page; for a stable walk, send sort=id and follow links.next without page.
Filters
- =
- equals
- [in]
- any of a comma-separated list
- [gte][lt]
- at least, less than
- [ne]
- not equal
Creation timestamp. Pair with sort=id for a stable full export.
Interval new subscriptions of this type are billed at by default.
A comma-separated list of at most 100 values.
yearlymonthlyone-time
New values may be added.
Search
Sorting
| Key | Sorts by |
|---|---|
sort_order | Position in the catalogue, as ordered in plnnrly. This is the default sort. |
name | Subscription type name, A→Z. |
id | Id, ascending. An id never changes, so use this for a stable full export. |
updated_at | Last-write timestamp; pair with the id tiebreaker for sync. |
Prefix a key with - for descending.
Other
Request headers
A correlation id of your own. It is recorded in our logs next to the server's request id but never returned: the response header always carries the server's id. A value that does not match the pattern is discarded silently, never rejected.
Response 200
Returns a page of SubscriptionTypeList rows.
The rows, each a SubscriptionTypeList.
per_page, next_cursor, prev_cursor, total, current_page, last_page.
self, next, prev.
Each row is a SubscriptionTypeList: 12 fields.
Headers
ETag- A weak validator (
W/"…") of the rendered page. RateLimit- The IETF
httpapi-ratelimit-headersform of your remaining allowance on the tightest bucket this request touched. RateLimit-Policy- The ceiling and window of that bucket, as
<limit>;w=<seconds>. X-Request-Id- The server-generated ULID correlating this response with our logs.
Every response also carries Cache-Control, Vary, X-Content-Type-Options, X-Plnnrly-Api-Version, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset. Headers and versioning
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.
Errors
8 errors every operation can return: 304, 400, 401, 404, 406, 429, 500, 503
304 Not modified.
400 Bad request.
idempotency-key-requiredinvalid-cursorinvalid-query-parametermalformed-requestunsupported-parameter
401 Unauthenticated.
404 Not found.
406 Not acceptable.
429 Too many requests.
500 Server error.
503 Service unavailable.
This path allows GET, POST. Anything else answers 405.
Something wrong or missing on this page? Tell us