Skip to main content
PATCH
Update a Loop routing rule

Authorizations

Authorization
string
header
required

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.

Path Parameters

id
string<uuid>
required

Workspace-scoped Loop resource ID.

Body

application/json
name
string
required
Required string length: 1 - 120
active
boolean
required
steps
object[]
required
Required array length: 1 - 25 elements
schedule_enabled
boolean
default:false
schedule_timezone
string | null

IANA timezone, or null to inherit the workspace timezone.

weekly_availability
object

Response

Updated routing rule.

data
object
required