Update the organization's report settings (org/me write)
The WRITE half of the org “org/me” settings surface. Sets the org’s writable preferences — today the Observe REPORT timezone (reportTimezone). The report timezone is the first source in the reporting-tz precedence chain: when set, the app applies it (over the browser tz) as the default ?tz= on every metric query, the day-bucket axis labels, the report schedule’s default tz, and the print/PDF window; when unset, the client falls through to the browser tz. A non-empty reportTimezone MUST be a valid IANA zone (an unknown/malformed zone is rejected 400); an empty string CLEARS the preference (revert to the browser-tz default). Org-scoped: writes the caller’s OWN organization row. Available to any authenticated principal (dual-auth) — no special scope is required.
Authorizations
Flowyte secret API key (Authorization: Bearer flowyte_sk_live_…). Scope-gated; is scoped to your organization — a key can never reach another tenant. The listed scopes in each operation's apiKey requirement are the scopes that key must hold. The tokenUrl is nominal: keys are minted in the dashboard.
Body
At least one writable field must be present (reportTimezone and/or callRecording); an all-empty body is a 400. Each field is applied independently.
A valid IANA timezone (e.g. America/New_York) to set as the org's Observe report timezone, or an empty string to CLEAR the preference (revert to the browser-tz default). Max 64 chars; the non-portable Local alias is rejected.
The org's call-recording preference (customer opt-in + retention). Both sub-fields are optional — an omitted sub-field keeps the stored value (toggle-only / retention- only PATCH). PLUMBING ONLY: the recording pipeline is globally gated OFF, so this is stored and honored but records nothing until the pipeline is enabled.