Change an own second factor
Description, default and status of an own second factor - with a session only.
Changes the account. Agents say what will happen and wait for an explicit yes before calling it.
Not offered over MCP - only to programs over REST.
Authentication
One of X-API-Key, Authorization: Bearer … - never more than one in a request. More
Request body JSON; unknown fields are refused
Send at least 2 field(s).
tfa_idinteger | stringrequiredThe factor, from access/tfa/list.
descriptionstring | nullis_defaultbooleanstatusstringinactive: kept, but not asked for at sign-in.
Response in data; the rest of the body as on every call
tfa_idintegerrequiredtypestringrequiredoath-totp: a code from an authenticator app; fido-u2f: a security key.
statusstringrequiredinactive: kept, but not asked for at sign-in.
descriptionstring | nullrequiredWhat the customer wrote about it (his description), null if nothing - not its name or user name.
is_defaultbooleanrequiredThe one the sign-in asks for first.
created_atstring | nullrequiredStatuses
200Success.400The request does not match the declared input schema.401No credential was presented, or it was not recognised.403The credential is not permitted to use this operation.500The server failed. Nothing about the request was wrong. Whether a change took effect is not known - check before trying it again.503The channel this operation forwards through is unavailable.