Read a subscription line
GEThttps://
Returns one subscription line in the detail view.
Access
- Token scope
- api:
read: customer_subscriptions Without it:
403 insufficient-token-scope. - Permission
- customer_subscriptions::
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.
- 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
The description is published exactly as stored, with any {{$domain}}-style placeholders unresolved: those are filled in only when a renewal turns the line into an invoice row. Lines are soft-deleted, so a deleted line is 404 unless trashed=with or trashed=only is passed; trashed=only 404s a live line. This flat path performs no lookup of the parent subscription: a line is readable by id to any caller holding customer_subscriptions::read, which is what plnnrly does too.
Path parameters
Query parameters
Unknown parameters are refused with 400, naming the parameter.
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 SubscriptionItem in the detail view.
Headers
ETag- A strong validator of exactly this representation.
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
The subscription this line belongs to. Taken from the path on create and never writable afterwards: a line cannot be moved to another subscription.
The subscription this line belongs to.
The kind of record subscribable points at; it says which branch of subscribable applies.
subscription_product
New values may be added.
What this line sells. Rendered as {"id": N} until named in ?include=subscribable, which additionally requires the read permission and token scope of the subscription_products prefix. Lines that bill a hosting domain or a server carry a subscribable_type this API publishes no shape for, and keep the {"id": N} form however they are requested; identify those from subscribable_type and subscribable_id yourself. Null on both halves is a free-text line priced by hand.
Which form you get depends on subscribable_type.
subscription_productSubscriptionProductSummary
The line text, as printed on the invoice a renewal generates. May contain placeholders such as {{$domain}}; the API publishes the raw stored text and those are resolved only at invoice time.
Cost price per unit, for margin bookkeeping only. It feeds neither generated amount below and appears on no invoice.
2 decimal places, not negative
Sales price per unit, excluding VAT. This is what actually bills: a renewal copies it into the generated invoice row's unit price.
2 decimal places, not negative
VAT on this line, computed by the server: quantity x sales_price x vat_rate / 100. Read-only.
2 decimal places, may be negative
Line total including VAT (quantity x sales_price plus the VAT above), computed by the server. Note this is the opposite convention from SalesInvoiceRow.total_amount, which excludes VAT: adding VAT to this value double-counts it. Read-only.
2 decimal places, may be negative
Position of the line within its subscription, and the default sort key. Assigned on create; there is no way to reorder lines through the API. Only the ordering is meaningful: values are not unique across subscriptions.
Exact Online article identifier this line bills against. Optional: a renewal falls back to the subscription product's own Exact values and then to the organisation's Exact defaults, so leaving it empty does not break the sync.
Last-write timestamp; use for incremental sync. This is also the ETag revision: a subscription line 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, PATCH, DELETE. Anything else answers 405.
Something wrong or missing on this page? Tell us