Create or update a device token

Operation boundary

Caller: Trusted backend only
Scope: The token is persisted cluster-wide; for a Master device, the handling node starts closing old sessions after about 10 seconds.
Success: A 200 response means the token write completed, not that old sessions are already closed.

POST/user/token

Upserts one UID/device token; default Gateway authentication requires later CONNECT credentials for the same UID and device category to match it.

Request Body

application/json

User, device, and token metadata to store.

TypeScript Definitions

Use the request body type in TypeScript.

Device-token update parameters.

uid*string

User ID whose device token is created or updated; it must not contain @, #, or &.

Length1 <= length

token*string

Opaque token persisted for this user and device category; the default Gateway requires later CONNECT credentials to match it exactly.

Length1 <= length

device_flag?integer

Device category; 0=APP, 1=Web, 2=PC, and 99=system, defaulting to 0 when omitted.

Formatuint8

Range0 <= value <= 255

Default0

device_level?integer

Same-category device conflict level; 0=Slave and 1=Master, defaulting to 0 when omitted.

Formatuint8

Range0 <= value <= 255

Default0

[key: string]?any

{  "status": 200}