Get one subscription
const url = 'https://api.nsin.cloud/subscriptions/1';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.nsin.cloud/subscriptions/1 \ --header 'Authorization: Bearer <token>'{id} is the numeric subscription id from GET /subscriptions, never a
domain: subscriptions are per domain, and every purchase, switch and renewal
leaves its own row, so expired, cancelled and superseded ones stay
readable here indefinitely. The lookup is bound to your own user_id, so a
subscription on a domain that was merely shared with you is a 404 — read
that one through GET /domains/{domain}/subscription, which admits shared
members. The payload is an envelope rather than a bare subscription:
subscription (carrying effective_features, plus the quota window while it
is active or in grace), period_statement, and invoices for this
subscription, newest id first. period_statement is the newest frozen
statement of this subscription; if it never closed one and is still active
or in grace, the field falls back to a live estimate built for the domain’s
current subscription, so compare the statement’s subscription_id with
{id} before attributing it. In every other case it is null.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Responses
Section titled “ Responses ”Subscription.
A plan attached to one domain. Entitlements are not read from the
plan directly — use GET /domains/{domain}/features, which resolves any
per-subscription overrides.
object
The plan this subscription is on.
object
The billing term purchased.
object
For example active, expired, grace or cancelled.
Traffic-allowance reset cadence, frozen at purchase time so later plan changes cannot shift an existing subscriber’s quota window.
The free trial granted at signup. Downgrades to the free plan on expiry rather than entering grace.
Example generated
{ "id": 1, "user_id": 1, "domain_id": 1, "domain_name": "example", "plan_id": 1, "plan": {}, "plan_term_id": 1, "plan_term": {}, "status": "example", "started_at": "2026-04-15T12:00:00Z", "expires_at": "2026-04-15T12:00:00Z", "grace_until": "2026-04-15T12:00:00Z", "auto_renew": true, "quota_reset_days": 1, "is_trial": true}Missing, malformed, revoked or expired API key, or a key whose owning
user row is gone. A key whose owning account has merely been deactivated
is not this: that is 403 with code: account_suspended, because the
credential itself is intact and re-issuing it changes nothing.
The error shape used by every endpoint. error is always present. code
is present only on the failures that have one — do not require it, and do
not parse error to recover it.
object
Human-readable description of what went wrong.
Stable machine-readable reason. Present on some failures only; the
wording of error may change, this will not.
account_suspended—403. The account behind the credential has been switched off, by an admin or by its provider. Every authenticated route answers this, so treat it as terminal rather than retrying.domain_disabled—409, not403. You have every right to the operation; the domain is simply switched off and is not being served, so its configuration cannot change. It stays readable, and writes work again once it is enabled.managed_by_reseller—403. The account is a reseller’s client and this surface belongs to its provider. See If your account is managed by a reseller.invite_email_mismatch—403fromPOST /invites/{token}/accept. The invitation was addressed to a different email; the body also carriesinvited_email, masked.
A panel session — not an API key — can additionally see
session_check_failed on a 503, which means the session could not
be verified, not that it is invalid. Retry it; do not discard the
token.
Examples
{ "error": "invalid API key"}No such subscription on this account.
The error shape used by every endpoint. error is always present. code
is present only on the failures that have one — do not require it, and do
not parse error to recover it.
object
Human-readable description of what went wrong.
Stable machine-readable reason. Present on some failures only; the
wording of error may change, this will not.
account_suspended—403. The account behind the credential has been switched off, by an admin or by its provider. Every authenticated route answers this, so treat it as terminal rather than retrying.domain_disabled—409, not403. You have every right to the operation; the domain is simply switched off and is not being served, so its configuration cannot change. It stays readable, and writes work again once it is enabled.managed_by_reseller—403. The account is a reseller’s client and this surface belongs to its provider. See If your account is managed by a reseller.invite_email_mismatch—403fromPOST /invites/{token}/accept. The invitation was addressed to a different email; the body also carriesinvited_email, masked.
A panel session — not an API key — can additionally see
session_check_failed on a 503, which means the session could not
be verified, not that it is invalid. Retry it; do not discard the
token.
Example
{ "error": "read-only API key"}The key exceeded its request budget (300 requests per minute by default).
The error shape used by every endpoint. error is always present. code
is present only on the failures that have one — do not require it, and do
not parse error to recover it.
object
Human-readable description of what went wrong.
Stable machine-readable reason. Present on some failures only; the
wording of error may change, this will not.
account_suspended—403. The account behind the credential has been switched off, by an admin or by its provider. Every authenticated route answers this, so treat it as terminal rather than retrying.domain_disabled—409, not403. You have every right to the operation; the domain is simply switched off and is not being served, so its configuration cannot change. It stays readable, and writes work again once it is enabled.managed_by_reseller—403. The account is a reseller’s client and this surface belongs to its provider. See If your account is managed by a reseller.invite_email_mismatch—403fromPOST /invites/{token}/accept. The invitation was addressed to a different email; the body also carriesinvited_email, masked.
A panel session — not an API key — can additionally see
session_check_failed on a 503, which means the session could not
be verified, not that it is invalid. Retry it; do not discard the
token.
Examples
{ "error": "rate limit exceeded"}