Subscriptions
A subscription is what entitles a customer to a live response — without an active one, callouts are rejected. It’s a central part of any integration: keep your active users in sync with their AURA subscriptions.
Each subscription has a subscriptionTypeId and a validity window (validFrom /
validTo):
- Discover types —
GET /panic-api/v2/subscriptions/subscriptionTypes. White-label web signup usesWEB_SIGNUP_SINGLE(orWEB_SIGNUP_FAMILY). - Activate —
POST /panic-api/v2/subscriptions; renew withPUT, cancel withDELETE. - Read back —
GET /panic-api/v2/customers/{customerId}/subscriptionsfor a customer’s subscription (rate-limited: ~50 requests per 10 seconds per customer source, then429), orGET /panic-api/v2/subscriptions/{subscriptionId}for a subscription with its linkeddependents[]— useful for family plans. - Family plans link dependants to a main member; if the main member’s subscription lapses, dependants lose access too.
A subscription has no status field. It is active when the current time is
within validFrom–validTo and CancelledDate (note the capital C) is
null. Derive “active” from those fields rather than looking for a status.
Lapsed or cancelled subscriptions can’t be recovered — create a new one to re-subscribe a customer.