Update analytics settings
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.
apiKeyAuthorizationBearer <token>An API key from the Developers page. rhq_test_ keys reach the sandbox, rhq_live_ keys the live side.
application/json- body
replayEnabled*booleanFalse stops every future dashboard recording
Success
application/json- response
Success
replayEnabled*booleanWhether the dashboard may send PostHog session replay for this account - off for every account flagged internal in the admin panel, whatever this reseller's own setting is, and otherwise this reseller's own choice. A rejected cookie banner or a deployment with no PostHog key configured sends nothing either way, which this field does not know about
curl -X PATCH "https://example.com/v1/account/analytics" \ -H "Content-Type: application/json" \ -d '{ "replayEnabled": true }'{ "replayEnabled": true}Update domain-order settings PATCH
The registrant every order falls back to, absent a per-order one; `POST /domains` can still send its own for a single order, and is refused with `registrant_required` when there is neither. `null` clears it. Changing any field of a contact already stored drops the registrar's handle and validation for it; sending back the exact same contact keeps them. `privacyByDefault` adds WHOIS privacy to new registrations wherever the ending offers it. `autoRenewByDefault` turns auto-renew on for new registrations. `digestEnabled` turns the weekly expiry digest email off. Live and sandbox keep their own.
Re-prove a strong credential POST
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.