Read a customer subscription
GEThttps://
Returns one subscription 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
Subscriptions are soft-deleted, so a deleted subscription is 404 unless trashed=with or trashed=only is passed; trashed=only 404s a live subscription. Its lines are not embedded: follow links.items, and its invoices are at sales-invoices?filter[customer_subscription_id]={id}.
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 CustomerSubscription 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 customer this subscription belongs to. Expanding it with ?include=customer additionally requires the customers::read permission and a token scope covering the customers prefix.
The subscription type this subscription is an instance of, which is also where its displayed name comes from. Expanding it with ?include=subscription_type additionally requires the subscription_types::read permission and a token scope covering the subscription_types prefix.
What this subscription covers, as free text. This is the field ?q= searches, and it is also what a generated invoice line falls back to.
Lifecycle status. Only an active subscription is picked up by the renewal run; the other three are inert.
pendingactivecancelledexpired
New values may be added.
How often the subscription is invoiced. one-time forces auto_renew to false, because a one-off has no next period to move on to.
yearlymonthlyone-time
New values may be added.
First day the subscription runs from, as a zone-free calendar date. Newest first is the default sort.
First day of the period to be invoiced next. Omit it on create and the server fills it with starts_at, so the first period is billable; the renewal run advances it by one interval each time it invoices. Null makes the subscription invisible to that run (it is skipped, silently), so a subscription that should never auto-invoice is expressed this way.
Day the subscription was cancelled, null while it has not been. It is a record of the cancellation date only: nothing derives status from it.
Whether the renewal run may invoice this subscription again. A one-time subscription is always false: it is forced on every save, so sending true together with billing_interval=one-time succeeds and comes back as false rather than failing.
Exact Online subscription this one maps to, by Exact's own external identifier, not by a local id. Written by the sync; null when the subscription has never been synced.
Day the subscription was last invoiced, null until it has been. Maintained by the renewal run.
Last-write timestamp; use for incremental sync. It also feeds the ETag revision, because a customer subscription 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