List Support Push Subscriptions
GET/api/support/push/subscriptions
Lists the devices the signed-in user has registered for push notifications, newest first. A caller only ever sees their own devices.
support:readGrant this scope to your token under Settings → Developer → Personal Access Tokens.
The endpoint is returned in full so a client can recognise its own device in the list — compare it against the endpoint of the subscription the browser currently holds. The encryption keys are never returned; the browser already has them.
Response fields (data[])
id(integer) — the device's idendpoint(string) — the push service URL this device was issued. It identifies the device everywhere in this folderuser_agent(string, nullable) — the label sent when the device registered, so one device can be told from anotherlast_used_at(string, nullable, ISO 8601 UTC) — when a notification was last delivered to this device;nulluntil the first one is sentcreated_at(string, ISO 8601 UTC) — when the device was registered
This endpoint does not require tenant context — a device is registered once and covers every tenant the caller works in.
Authentication: Bearer token with the support:read scope, or an authenticated session.
Request
Responses
- 200
- 401
- 403
- 429
OK
Response Headers
Unauthorized
Response Headers
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.