Update rate limit
Update the rate limiting configuration for a load balancer. Rate limiting restricts each client IP to 100 requests per minute per hostname across the load balancer domains. When a client exceeds the limit, the configured action is applied: challenge requires the visitor to pass a managed challenge for 5 minutes, throttle blocks requests only while the rate stays above the limit, and ban blocks the client IP for 5 minutes. Changes are synced to the edge network as part of the request. Returns the updated rate limit state.
Authorizations
API key authentication. Pass your API key as a Bearer token in the Authorization header.
Path Parameters
Load balancer identifier
^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"fb5e5168-4281-4bec-94c5-0d1584e9e657"
Body
Whether rate limiting should be active
true
Mitigation action to apply when a client IP exceeds the limit of 100 requests per minute. challenge - visitors must pass a managed challenge for 5 minutes. throttle - requests are blocked only while the rate stays above the limit. ban - the client IP is blocked for 5 minutes.
challenge, throttle, ban "challenge"
Response
Default Response
Whether rate limiting is currently active
true
Mitigation action applied when a client IP exceeds the limit of 100 requests per minute. challenge - visitors must pass a managed challenge for 5 minutes. throttle - requests are blocked only while the rate stays above the limit. ban - the client IP is blocked for 5 minutes.
challenge, throttle, ban "challenge"