Update routing rule

PUT/omnichannel/routing-rules/{id}

Updates an existing routing rule's name, priority, conditions, actions, or active status. New conditions/actions completely replace the stored JSON when supplied; omit the fields to retain existing values.

Request

Path parameters

Name	Type	Required	Description
id	integer	Yes	The numeric ID of the routing rule to update.

Request body

Content type application/json (required).

Field	Type	Required	Description
name	string	Yes	Human-readable rule name. Max length: 180
priority	integer	No	Lower numbers are evaluated first. Default: 100 · Minimum: 1
is_active	boolean	No	Set to false to disable without deleting. Default: true
conditions_json	string	No	JSON-serialised array of condition objects. Each object should have "field", "op", and "value" keys.
actions_json	string	No	JSON-serialised array of action objects. Each object should have a "type" key and any required parameters.

Example

{
  "name": "VIP customer — assign to senior agents (revised)",
  "priority": 5,
  "is_active": true
}

Responses

200 Routing rule updated

404 Routing rule not found

Example request

curl -X PUT "https://{tenant}.faciotech.net/api/v1/omnichannel/routing-rules/{id}" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -d '{"name": "VIP customer — assign to senior agents (revised)", "priority": 5, "is_active": true}'