Re-prove a strong credential
Confirms a sensitive action by password (and a code, if two-factor is on). A passkey instead re-asserts through /api/auth/passkey/verify-authentication. Either one starts a short grace window during which a gated action proceeds without being asked again.
apiKeyAuthorizationBearer <token>An API key from the Developers page. rhq_test_ keys reach the sandbox, rhq_live_ keys the live side.
application/json- body
password*string1 <= lengthcode?string1 <= lengthbackupCode?string1 <= lengthSuccess
application/json- response
Success
ok*truetrueexpiresAt*stringcurl -X POST "https://example.com/v1/step-up" \ -H "Content-Type: application/json" \ -d '{ "password": "string" }'{ "ok": true, "expiresAt": "string"}Update analytics settings PATCH
Switches dashboard session replay off for this account, or back on. Has no effect on an account flagged `internal` in the admin panel, which never records whatever this is set to.
Get the account overview GET
What you hold, what needs you and what renews by itself over the next 30 days, counted across every page. Each part your role cannot see comes back empty.