Update low-credit warning preferences
Updates the personal low-credit warning threshold and delivery channels for the user associated with this credential. At least one delivery channel must remain enabled while warnings are enabled. This preference follows the user across workspaces. A user-owned API key or OAuth token is required; service-account credentials are rejected. Required scope: settings:write.
Authorizations
API key (fam_..., created under Settings → API Keys) or an OAuth 2.0 access token (fam_at_...). REST operations also require API Access for the credential's workspace. Keys can be restricted to scopes such as assistants:read, calls:write, campaigns:write, automations:read, dashboards:read, dashboards:write, leads:write, segments:write, loop:read, loop:write, phone_numbers:write, sip_trunks:write, knowledge:write, voices:read, billing:read, settings:write, platform:read, platform:write; a *:write scope implies the matching *:read. Automation and dashboard endpoints also accept the legacy calls:* scope. Keys without scope restrictions have full access within the workspace's available capabilities.
Body
Whether personal low-credit warnings are enabled.
Send the warning when the available balance reaches this number of credits.
1 <= x <= 1000000000Deliver the warning through browser push notifications.
Deliver the warning to the account email address.
Response
Updated personal low-credit warning preferences.