Protect your application with Service Rate Limits

Service Rate Limits makes it easy to leverage Twilio's battle-test rate limiting services to protect your deployment. With Service Rate Limits, you can define the keys to meter and limits to enforce when starting verifications. This enables you to rate limit on end-user IP addresses, session IDs or other unique IDs that are important to your application. Together with Verify's built-in platform protections Service Rate Limits give you turnkey protections with flexibility.

必要なもの:

1. Create a Verification Service

Create a Rate Limit

The Service Rate Limit resource represents the key that your application will provide when starting a phone verification request. For example, you may create a rate limit for an end-user IP address to prevent a malicious bot.

Selecting Properties to Rate Limit

Rate Limits provide the capability to enforce limitations, but they are not prescriptive about what properties to limit. Determining which properties to limit is determined by how and where you have deployed Verify. For example, rate limiting by IP Address makes sense for a mobile consumer application where the End User IP address is easily accessible. But rate limiting on IP Address is less effective if Verify is deployed behind a reserve proxy without access to the End User IP Address.

Examples of properties to rate limit include:

• End User IP Address
• Geolocation of End User IP Address
• 電話番号
• Phone Number Country Code (ex +1 in the US or +44 in GB)
• Session ID
• User Agent

The flexibility afforded by Rate Limits in Verify means that you can enforce limits on "mixed" properties simply by concatenating values together. This is particularly helpful for enforcing rate limits on properties that are highly correlated.

Possible examples of highly correlated properties include:

• Phone Number Country Code and Geolocation of End User IP Address
• Phone Number and Geolocation of End User IP Address
• Phone Number and End User IP Address

Create a Bucket

The Service Rate Limit Bucket resource 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.

Start a Phone Verification

To use the Rate Limits we need to update the request that starts phone verifications to include the values we want to limit. To do this we will add the new `RateLimit` parameter to our request.