Update Routing Rule
Edit a routing rule. The body uses the same shape as create — the rule is replaced wholesale (the platform doesn't merge); pass the full state you want, including the conditions array.
Changes take effect on the next request — there's no caching window. Use enabled: false if you want to suspend a rule without losing its config.
Path parameters
uuid from /endpoints.uuid from the list. Resolved under this endpoint only.Deprecated: the legacy integer id is still accepted in the path until the sunset, answered with Deprecation and Sunset headers. Use the uuid.
Request body
Same fields as create: name, priority, target_agent_id / target_agent_tags, enabled, fallback, conditions. The whole rule is replaced — passing only some fields zeroes the rest, and the conditions are replaced by the ones you send. So the update is validated like a create: name, at least one (non-null) condition, and target_agent_id or target_agent_tags are required.
Response (200 OK)
The rule as stored, read back after the write: its uuid, its real created_at / updated_at, and its conditions as saved. Same shape as a list entry.
Deprecated: until the sunset this response also carries the legacy integer id and *_id fields. Don't use them; read uuid and the *_uuid fields.
Errors
name (Rule name is required), empty conditions (At least one condition is required) or a null entry in it (Invalid condition: conditions[N] is null), neither target_agent_id nor target_agent_tags set (Either target_agent_id or target_agent_tags is required); an application endpoint (Routing rules are not supported for agentless (static hosting) endpoints.), or an integer rule id after the sunset (integer_id_unsupported).endpoint_routing_rules entitlement.Routing rule not found)."code": "quota_paused").