Update Rate Limit Condition
Rewrite one condition of a rate-limit rule. This is a full write of the condition, not a patch: send type, operator and value every time (an omitted logical_operator becomes AND). The condition keeps its uuid and its place in the rule's evaluation order.
The body and its validation are the same as Add Rate Limit Condition. The change is announced to the edges in every region as soon as it is saved. Requires the rate_limits:update permission in the active account and the custom_rate_limits entitlement.
Path parameters
uuid from List Rate Limits.Deprecated: the legacy integer ids are still accepted in the path until the sunset, answered with Deprecation and Sunset headers. Use the uuids.
Request body
exists / not_exists.AND (default) or OR: joins this condition to the next one.Response (200 OK)
The condition as stored: uuid, rule_uuid, condition_type, operator, condition_value, logical_operator and created_at (when it was first added). Sending the values it already has is not an error: you get the same 200.
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
Invalid JSON payload); a condition that fails validation — "error": "Bad request" with the reason in detail; or an integer id after the sunset (integer_id_unsupported).rate_limits:update; your plan doesn't include custom_rate_limits ("code": "entitlement_required"); or the account is suspended (account_suspended).Rate limit rule not found (no such rule in the active account), or Condition not found (no such condition, or it belongs to another rule).quota_paused: the rule is paused over your plan's limits and is read-only.Content-Type: application/json header.