neosourceDocs
Search docs

Unlink an OAuth identity

DELETE/api/user/identities/{identity_id}

unlinkIdentity

Refuses to remove the last login method on the account (set a password first). **Requires sudo-mode** (plans/auth-flows.md slice #5) — *unless* the account holds no step-up credential yet (a passwordless / OAuth-claimed account with no password, TOTP, or passkey, which has no way to acquire sudo). The last-login-method guard is enforced independently of this carve-out, so a zero-credential account can never strand itself: the carve-out only lets it past the sudo gate, after which unlinking its sole remaining identity still returns `409`. Once any step-up credential exists this is sudo-gated again. Returns `403 { error: "sudo_required", challenge: "password"|"totp" }` if the sudo window has elapsed.

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

curl

curl -X DELETE 'https://neosource.dev/api/user/identities/IDENTITY_ID' \
  -b 'ns_session=$NEOSOURCE_SESSION'

fetch

fetch("https://neosource.dev/api/user/identities/IDENTITY_ID", {
  method: "DELETE",
  credentials: "include",
});

Path parameters

identity_idrequired

string

Responses

204Unlinked

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
  • 404Not Found — one of: not_found
  • 409Conflict — one of: already_exists, conflict
  • 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