| mx_delete_device | R Documentation |
Removes a device and invalidates its access token. Most homeservers
protect this with user-interactive authentication: the first call
fails with M_FORBIDDEN or a 401 carrying a flows object, and
the caller retries with a completed auth payload, e.g.
list(type = "m.login.password", identifier = list(type =
"m.id.user", user = "bot"), password = "...", session = "<from the
401>"). mx.api deliberately does not automate that exchange.
mx_delete_device(session, device_id, auth = NULL)
session |
An "mx_session" object. |
device_id |
Character. The device to delete. |
auth |
List or NULL. Completed user-interactive auth payload. |
Invisibly TRUE on success.
## Not run:
mx_delete_device(s, "OLDDEVICE", auth = list(
type = "m.login.password",
identifier = list(type = "m.id.user", user = "bot"),
password = "secret"
))
## End(Not run)
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.