Record where to show this device a message alert
Not the push token. The push token wakes the device for a call (a PushKit VoIP token on iOS, an FCM token on Android). The alert token is a regular APNs token (iOS) that draws a banner for a message or mention. A device carries both, because they are different addresses for different pushes. Call this on every launch: the token rotates silently on reinstall, restore and app-data clear. It is stored as given and never returned by any endpoint.
Authorization
deviceAuth A per-device secret issued by POST /v1/devices/enroll, presented as
Authorization: Device <secret>.
A distinct scheme rather than another bearer flavour: the bearer namespace already carries workspace API keys and session JWTs, and a device secret authorises far less than either — it can mint a WebRTC token for its own identity and report presence, and nothing else.
In: header
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
curl -X PUT "https://example.com/v1/devices/alert-token" \ -H "Content-Type: application/json" \ -d '{ "alert_token": "string" }'{ "ok": true}Forget where to wake this device DELETE
Call on sign-out, or when notification permission is withdrawn. A token left behind that can no longer ring is not harmless: every wake attempt against it is silent waste. Revoking a device clears its token too.
Forget where to show this device alerts DELETE
Call on sign-out, or when notification permission is withdrawn. Idempotent: clearing a device that has no alert token still answers 204.