A Bucket defines the limit that should be enforced against the key it is associated with. A Rate Limit can have multiple buckets so that you can detect and stop attacks at different velocities.
Prerequisites:
If you are just getting started with Rate Limits in Verify we recommend checking out our guide on Using Verify Service Rate Limits to Protect Your Application before diving into the API.
POST https://verify.twilio.com/v2/Services/{ServiceSid}/RateLimits/{RateLimitSid}/Buckets
The Twilio-provided string that uniquely identifies the Rate Limit resource.
GET https://verify.twilio.com/v2/Services/{ServiceSid}/RateLimits/{RateLimitSid}/Buckets/{Sid}
The Twilio-provided string that uniquely identifies the Rate Limit resource.
GET https://verify.twilio.com/v2/Services/{ServiceSid}/RateLimits/{RateLimitSid}/Buckets
The Twilio-provided string that uniquely identifies the Rate Limit resource.
How many resources to return in each list page. The default is 50, and the maximum is 1000.
POST https://verify.twilio.com/v2/Services/{ServiceSid}/RateLimits/{RateLimitSid}/Buckets/{Sid}
The Twilio-provided string that uniquely identifies the Rate Limit resource.
Number of seconds that the rate limit will be enforced over.
DELETE https://verify.twilio.com/v2/Services/{ServiceSid}/RateLimits/{RateLimitSid}/Buckets/{Sid}
The Twilio-provided string that uniquely identifies the Rate Limit resource.