neosourceDocs
Search docs

Disable TOTP

POST/api/auth/totp/disable

totpDisable

Requires both the current password AND a valid TOTP code, defending against an attacker with a leaked session. **Requires sudo-mode** (plans/auth-flows.md slice #5). Returns `403 { error: "sudo_required", challenge: "password" }` if the sudo window has elapsed.

Requires authentication using a session cookie — see tokens and scopes.

curl

curl -X POST 'https://neosource.dev/api/auth/totp/disable' \
  -b 'ns_session=$NEOSOURCE_SESSION' \
  -H 'Content-Type: application/json' \
  -d '{"password":"string","code":"string"}'

fetch

fetch("https://neosource.dev/api/auth/totp/disable", {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
  },
  credentials: "include",
  body: JSON.stringify({"password":"string","code":"string"}),
});

Request bodyrequired

application/json

TotpDisableRequest

object

coderequired

string

passwordrequired

string

additional propertiesnot allowed

Responses

204Disabled

403Forbidden — one of: forbidden, sudo_required

application/json

one of
  • ErrorForbidden
  • SudoRequiredError

    object

    Wire shape of the 403 a sudo-gated endpoint returns when sudo is missing or expired. `challenge` tells the SPA which sudo-prove endpoint to call.

    challengerequired

    string

    Which sudo-prove endpoint the account should use: `"passkey"` (`/api/auth/sudo/passkey/{start,finish}`), `"password"` (`/api/auth/sudo/password`), or `"totp"` (`/api/auth/sudo/totp`), chosen from the account's registered credentials — passkey first when present, since it is both the strongest credential and the least friction. A hint for which prompt to show first, not an authorization decision: each sudo route verifies its own credential regardless of what was advertised here, so a client may use a different one.

    errorrequired

    string

    Always `sudo_required` — this body exists to carry the extra fields that kind needs.

    "sudo_required"

    messagerequired

    string

Standard errors

Bodies documented once for the whole API — see standard errors.

  • 400Bad Request — one of: invalid_input
  • 401Authentication required
  • 429Rate limited — retry after the `Retry-After` header
  • 500Internal server error
  • 503Service temporarily unavailable / at capacity — retry after the `Retry-After` header
  • 504Gateway timeout — the request exceeded the server's handling budget