List push-subscriptions
GET /push-subscriptions
Per-user/organisation Web Push subscription (F3.PWA.01). Reuses the F3.CHATOPS.01 event catalog for push payloads. p256dh_key and auth_key are AES-256-GCM encrypted at rest (same scheme as BYOC cloud-credential / notification-channel) and are never returned by the API — only a masked ‘is_configured’ indicator.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Query Parameters
Section titled “Query Parameters ”Strapi REST filter syntax
object
Responses
Section titled “ Responses ”OK
object
object
Push service endpoint URL (unique per browser subscription, not a secret, but treated as sensitive since it identifies the device).
DEPRECATED plaintext field — retained read-only for pre-encryption legacy rows. New writes always go to encrypted_p256dh_key. NEVER returned by the API.
DEPRECATED plaintext field — retained read-only for pre-encryption legacy rows. New writes always go to encrypted_auth_key. NEVER returned by the API.
AES-256-GCM encrypted PushSubscription.keys.p256dh (F3.PWA.01) — same iv:authTag:ciphertext:salt format as BYOC cloud-credential (src/utils/credential-crypto.ts). NEVER returned by the API; decrypted only server-side by push-notifier for dispatch.
AES-256-GCM encrypted PushSubscription.keys.auth (F3.PWA.01). NEVER returned by the API.
Array of subscribed event-type strings. Canonical catalog (F3.CHATOPS.01/F3.PWA.01): ‘billing.payment_failed’, ‘billing.trial_ending’, ‘cloud-instance.provision_failed’, ‘alert.fired’. Empty/null = all events.
Browser User-Agent at subscribe time — helps the user identify which device/browser a subscription belongs to in settings.
object
object
Missing or invalid authentication
Not authorized (tenant scope or capability)