Rensei docs
API ReferenceNotifications

Revoke a push device token owned by the authenticated user.

Soft-revokes a device token by `id` or `token`. The revoke is bounded by the caller user id, so a foreign token is a silent no-op.

DELETE
/api/notifications/devices

Authorization

headerAuthorizationBearer <rsk_live_*>

Rensei API key presented as Authorization: Bearer rsk_live_. Required API-key scopes are recorded per operation in x-rensei-required-scopes.

Request Body

application/json
  1. body
id?string
Length1 <= length
token?string
Length1 <= length

Response Body

Revoke applied (revoked count; 0 when no owned row matched).

application/json
  1. response
revoked*number
Example Request
curl -X DELETE 'https://app.rensei.ai/api/notifications/devices' \  -H 'Content-Type: application/json' \  -d '{}'
Example Response
{  "revoked": 0}

Register (or refresh) a push device token for the authenticated user.

Upserts a per-user APNs or web-push device token. The write is scoped to the authenticated user; a credential with no user identity is rejected. Re-registering a live token bumps last-seen and refreshes its mutable fields.

Return the VAPID public key for browser web-push subscription.

Returns the server VAPID public key (null when web-push is not configured) so the client can call pushManager.subscribe without baking the key into the bundle.