DELETE
Unregister push token

Overview

The client calls this on:
  • Sign-out — to stop sending push to a device that’s no longer logged in.
  • Notification permission revoked — to keep the server-side record in sync with the device.
  • App uninstall preflight — best-effort only; FCM 410-GONE cleanup (see Push notification fan-out) is the real safety net.
Removing a token that is not on the user’s record returns 200 { removed: false } rather than 404. This is intentional: the client should not have to track whether a given token is currently registered.

Authentication

Bearer <accessToken> required. requireAuth + requireOnboarded middleware applied.

Path parameters

Query parameters

None.

Request body

None.

Response — 200 OK

Idempotent no-op:

Side effects

  • On removed: true: the (token) entry is pulled from the user’s pushTokens array.
  • On removed: false: no mutation.

Error responses

See also

curl